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

9m 54s

1660 CI pipeline executions

Computation time saved

42d 4h

Cache hit rate

90%

Protect cache integrity with sandboxing

Time to Green

51m 33s

Was 1h 2m, improved by 18%

Succeeded
30296
bb5d6d0e 🐛 Fixed statuses of posts not scheduled due to archived newsletter closes https://linear.app/ghost/issue/NY-1465 What ---- We don't publish scheduled posts for archived newsletters. Before this change, we'd fail the request from the scheduler and do nothing. Now, we fail the request from the scheduler _and_ unschedule the post, moving it back to a draft status. Why --- Two reasons: 1. This is arguably the correct behavior. This avoids posts that get stuck scheduled in the past until someone intervenes. 2. This prevents an endless scheduler loop. We reschedule all scheduled posts on server startup, which means that we'd keep asking the scheduler to do something it's guaranteed to fail. (There are some other solutions to this problem but they have worse product outcomes.) Testing ------- In addition to automated tests, I also checked this manually.
by Evan Hahn
E
Failed
30296
3c2cdca2 🐛 Fixed statuses of posts not scheduled due to archived newsletter closes https://linear.app/ghost/issue/NY-1465 What ---- We don't publish scheduled posts for archived newsletters. Before this change, we'd fail the request from the scheduler and do nothing. Now, we fail the request from the scheduler _and_ unschedule the post, moving it back to a draft status. Why --- Two reasons: 1. This is arguably the correct behavior. This avoids posts that get stuck scheduled in the past until someone intervenes. 2. This prevents an endless scheduler loop. We reschedule all scheduled posts on server startup, which means that we'd keep asking the scheduler to do something it's guaranteed to fail. (There are some other solutions to this problem but they have worse product outcomes.) Testing ------- In addition to automated tests, I also checked this manually.
by Evan Hahn
Failed
30296
cd390a17 🐛 Fixed statuses of posts not scheduled due to archived newsletter closes https://linear.app/ghost/issue/NY-1465 What ---- We don't publish scheduled posts for archived newsletters. Before this change, we'd fail the request from the scheduler and do nothing. Now, we fail the request from the scheduler _and_ unschedule the post, moving it back to a draft status. Why --- Two reasons: 1. This is arguably the correct behavior. This avoids posts that get stuck scheduled in the past until someone intervenes. 2. This prevents an endless scheduler loop. We reschedule all scheduled posts on server startup, which means that we'd keep asking the scheduler to do something it's guaranteed to fail. (There are some other solutions to this problem but they have worse product outcomes.) Testing ------- In addition to automated tests, I also checked this manually.
by Evan Hahn