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

8m 22s

352 CI pipeline executions

Computation time saved

3d 12h

Cache hit rate

25%

Time to Green

25m 51s

Was 28m 5s, improved by 8%

Succeeded
11360
e2dd3f50 fix(solid-query): don't re-create and refetch a removed query The read layer bumps its per-hook version signal on every cache event for its hash, 'removed' included, and the recompute that followed called `queryCache.build()`, putting the entry the caller had just deleted straight back. The resurrection was not passive: the rebuilt entry also re-pointed the still-live observer, whose mount-fetch policy then refetched and repopulated the key, so `removeQueries()` and `clear()` could not be made to stick while any hook observed the key. `query()` now reuses the entry it last read when the cache no longer holds that hash, and builds only when the hash is genuinely new. A removal leaves the cache empty and fires no fetch, while the mounted reader holds its last value until options change or a real entry returns through `setQueryData`, a refetch or a later mount. The resulting cache event sequence, entry count, data and fetch count are identical to react-query's for the same scenario, and to solid-query's at 6.0.0-rc.0. Fixes #11350
by Rizwan Saleem
R