Overview - Ghost

GhostWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

Ghost

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

GhostWorkspace

Agents
Replay
VCS
Self-Healing

Average execution time

11m 13s

1145 CI pipeline executions

Computation time saved

20d 13h

Cache hit rate

87%

Protect cache integrity with sandboxing

Time to Green

31m 58s

Was 42m 7s, improved by 24%

Succeeded
30811
377af2f8 Moved shutdown tracking to the whole send-email job no ref The batch sending service only tracked sendEmail in its in-flight set, so onShutdown resolved once the last batch settled, before emailJob wrote the email's terminal status. That write only survives shutdown today because the job runner happens to wait for the whole job; the email path should not depend on the runner's drain policy for its own bookkeeping. Tracking emailJob instead covers the status lock, the batch work and the terminal status write with a single tracker at the job boundary. It cannot hang shutdown: every phase past the send already runs under the collapsed shutdown retry budgets, and the `failed` write is skipped while shutting down.
by Fabien O'C...
F