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

629 CI pipeline executions

Computation time saved

15d 1h

Cache hit rate

89%

Protect cache integrity with sandboxing

Time to Green

53m 47s

Was 1h 8m, improved by 21%

Succeeded
30230
34f929a4 🐛 Fixed dropped newsletter recipients when batch creation is interrupted no ref If a container restarted while an email's batches were still being built, the next run treated the partial batch set as complete: sendEmail skipped createBatches whenever any batches already existed, silently abandoning the un-built tail of recipients. The email was then marked submitted with an email_count reflecting the pre-send estimate, so recipients below the interruption point were never batched or sent. createBatches is now idempotent. It reads the coverage a prior run already built (per segment: recipient count and the lowest built member id) and resumes each segment below that watermark, so re-running builds only the un-built tail and never duplicates. sendEmail always reconciles instead of skipping, and totalCount is seeded from existing coverage so the domain-warmup split and the email_count correction stay accurate. Batch creation also now aborts at a batch boundary on shutdown, mirroring the send loop, leaving a consistent partial that resumes on the next boot.
by Austin Bur...
Succeeded
30230
a26bfd72 🐛 Fixed dropped newsletter recipients when batch creation is interrupted no ref If a container restarted while an email's batches were still being built, the next run treated the partial batch set as complete: sendEmail skipped createBatches whenever any batches already existed, silently abandoning the un-built tail of recipients. The email was then marked submitted with an email_count reflecting the pre-send estimate, so recipients below the interruption point were never batched or sent. createBatches is now idempotent. It reads the coverage a prior run already built (per segment: recipient count and the lowest built member id) and resumes each segment below that watermark, so re-running builds only the un-built tail and never duplicates. sendEmail always reconciles instead of skipping, and totalCount is seeded from existing coverage so the domain-warmup split and the email_count correction stay accurate. Batch creation also now aborts at a batch boundary on shutdown, mirroring the send loop, leaving a consistent partial that resumes on the next boot.
by Austin Bur...
Succeeded
30230
df68025f 🐛 Fixed dropped newsletter recipients when batch creation is interrupted no ref If a container restarted while an email's batches were still being built, the next run treated the partial batch set as complete: sendEmail skipped createBatches whenever any batches already existed, silently abandoning the un-built tail of recipients. The email was then marked submitted with an email_count reflecting the pre-send estimate, so recipients below the interruption point were never batched or sent. createBatches is now idempotent. It reads the coverage a prior run already built (per segment: recipient count and the lowest built member id) and resumes each segment below that watermark, so re-running builds only the un-built tail and never duplicates. sendEmail always reconciles instead of skipping, and totalCount is seeded from existing coverage so the domain-warmup split and the email_count correction stay accurate. Batch creation also now aborts at a batch boundary on shutdown, mirroring the send loop, leaving a consistent partial that resumes on the next boot.
by Austin Bur...