Overview - Query

queryWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

query

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

queryWorkspace

Average execution time

3m 34s

599 CI pipeline executions

Computation time saved

3d 20h

Cache hit rate

32%

Time to Green

12m 12s

Was 15m 48s, improved by 23%

Succeeded
11469
194bc526 fix(solid-query): read undefined from a disabled query instead of suspending A read of a disabled query with nothing cached used to park on a promise that never settles. Nothing revives that promise — enabling the query or writing to the cache re-runs the compute and abandons it — so any consumer that waits on it rather than recomputing hangs: the SSR stream never completes (no interaction can enable the query), and a <Loading> boundary whose enabling control sits inside it replaces that control with the fallback. The read now returns `undefined` for that state, which is what React Query's `useQuery` returns for a disabled query. Enabling, a refetch or a cache write re-runs the compute and the read becomes a normal pending or settled read. Since the node already committed `undefined`, the first fetch after enabling holds the committed UI like any refetch; `isLoading` reports it, matching the `data: undefined, isLoading: true` shape. `data` widens to `TData | undefined` only for options that can disable the query (`enabled` that is not literally `true`, or a `queryFn` that may be `skipToken`) and have no `initialData`; a new `AlwaysEnabledOptions` overload keeps the suspending `TData` face for everything else. The same rule applies to `useInfiniteQuery`, `useQueries`, `queryOptions` and `infiniteQueryOptions`. A function `placeholderData` now receives the previous query's data for a disabled query, where the engine has no pending fetch to hold the previous value against, so `keepPreviousData` behaves as in React Query there. The hydration-window parks (adoption, priming, restore) are unchanged. Co-authored-by: Cursor <cursoragent@cursor.com>
by Ryan Carniato
R