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

1134 CI pipeline executions

Computation time saved

20d 21h

Cache hit rate

87%

Protect cache integrity with sandboxing

Time to Green

34m 29s

Was 45m 11s, improved by 24%

Succeeded
ber-3911-lag-review-fixes
0d93d5ec Merge 653709e0468d346e6b5e13d805b77a5b2651ef41 into b79666a3a6e87747472117b2a748f67ce6d03c5c
by Jonatan Sv...
Failed
30735
0d93d5ec Added lag reporting for email analytics event processing
by Jonatan Sv...
J
Succeeded
30735
490e4e3b Fixed analytics status e2e test to assert the initial pipeline state ref https://linear.app/ghost/issue/BER-3911 An earlier commit loosened this test on the assumption that sending a newsletter in another test could schedule the real analytics job in the shared process. It can't: the job scheduler skips scheduling whenever NODE_ENV starts with "test", and nothing in the e2e suites triggers a fetch directly. The pipelines are always in their initial state here, so the test now snapshots the body, which also pins lag being unknown before any fetch has run.
by Jonatan Sv...
J
Succeeded
30735
5026628e Changed the email analytics lag warning setting to lagWarningMinutes ref https://linear.app/ghost/issue/BER-3911 The threshold now applies to the opened, delivery and missing events pipelines, so openedJobLagWarningMinutes no longer described it. There is no fallback: an environment that overrides the old key needs to set emailAnalytics:lagWarningMinutes instead, or it gets the default of 30.
by Jonatan Sv...
J
Succeeded
30735
e249a8a0 Removed the config gate for the opened lag metric ref https://linear.app/ghost/issue/BER-3911 Metrics ship through the logging transports configured in loggingrc (a stdout line or an Elasticsearch document) and do nothing without them, so the opened lag metric is effectively a log line each fetch cycle. Gating it behind emailAnalytics:metrics:openedLag:enabled only added a setting to remember to turn on, so it is now always emitted with the lag warnings.
by Jonatan Sv...
J
Succeeded
30735
e249a8a0 Removed the config gate for the opened lag metric ref https://linear.app/ghost/issue/BER-3911 Metrics ship through the logging transports configured in loggingrc (a stdout line or an Elasticsearch document) and do nothing without them, so the opened lag metric is effectively a log line each fetch cycle. Gating it behind emailAnalytics:metrics:openedLag:enabled only added a setting to remember to turn on, so it is now always emitted with the lag warnings.
by Jonatan Sv...
J
Succeeded
30735
e249a8a0 Removed the config gate for the opened lag metric ref https://linear.app/ghost/issue/BER-3911 Metrics ship through the logging transports configured in loggingrc (a stdout line or an Elasticsearch document) and do nothing without them, so the opened lag metric is effectively a log line each fetch cycle. Gating it behind emailAnalytics:metrics:openedLag:enabled only added a setting to remember to turn on, so it is now always emitted with the lag warnings.
by Jonatan Sv...
J
Succeeded
30735
91456d19 Updated email analytics lag reporting to build on #30685
by Jonatan Sv...
J
Succeeded
30735
91501929 Fixed analytics status e2e test depending on background job state ref https://linear.app/ghost/issue/BER-3911 e2e-api files share a Ghost process, and sending a newsletter in an earlier test schedules the real analytics job on a five-minute cron. If it runs before this test, running, lagSeconds and the response length all change, so pinning them made the test depend on file order and timing. It now checks the response shape and matches content-length loosely.
by Jonatan Sv...
J