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 51s

299 CI pipeline executions

Computation time saved

9d 14h

Cache hit rate

21%

Time to Green

14m 5s

Was 17m 30s, improved by 20%

Succeeded
main
a16e71c7 fix(mutation-observer): snapshot mutateOptions before dispatching callbacks (#11945) * fix(mutation-observer): snapshot mutateOptions before dispatching callbacks When mutate() is called inside an onSuccess handler, this.#mutateOptions is overwritten before the subsequent onSettled call in #notify(). This causes onSettled to fire with the next mutation's callbacks but the current mutation's data and variables. Fix by snapshotting mutateOptions at the top of #notify() before any callbacks execute, so all three callbacks (onSuccess/onError/onSettled) see the same consistent options for the mutation that settled. Fixes #11451 * ci: apply automated fixes --------- Co-authored-by: Dominik Dorfmeister 🔮 <office@dorfmeister.cc> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by okxint
Succeeded
11945
62928170 fix(mutation-observer): snapshot mutateOptions before dispatching callbacks When mutate() is called inside an onSuccess handler, this.#mutateOptions is overwritten before the subsequent onSettled call in #notify(). This causes onSettled to fire with the next mutation's callbacks but the current mutation's data and variables. Fix by snapshotting mutateOptions at the top of #notify() before any callbacks execute, so all three callbacks (onSuccess/onError/onSettled) see the same consistent options for the mutation that settled. Fixes #11451
by okxint