Run details

queryWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix/solid-query-removed-query-resurrection
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

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

nx affected --targets=test:sherif,test:knip,test:docs,test:eslint,test:lib,test:types,test:build,build

Succeeded

read access token used

038398d811360

74%

Distribution saved time

3m 05s instead of 11m 44s.

Atomizer enabled

17 groups of tasks optimized.

© 2026 - Nx Cloud

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

queryWorkspace