Run details

GhostWorkspace

CI Pipeline Executions
- Current executionSucceeded
  send-email-shutdown-tracking
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

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.

nx run ghost-monorepo:lint:boundaries

Succeeded

4 CPU cores

read-write access token used

efb3038630811

© 2026 - Nx Cloud

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

GhostWorkspace