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

608 CI pipeline executions

Computation time saved

13d 21h

Cache hit rate

89%

Protect cache integrity with sandboxing

Time to Green

52m 29s

Was 1h 4m, improved by 19%

Succeeded
30517
bab3524f Updated publish request options with main Resolved the email API overlap while preserving sending-status queries and editor session-expiry handling. Updated the new analytics retry caller to use the shared payload shape.
by Steve Larson
Succeeded
30517
8ff77440 Fixed editor redirects through shared queries no ref Editor query hooks could still mount redirect-capable current-user, settings, and config observers behind callers that had opted out. Forwarding the same transport option through those hidden reads keeps an expired session in place, while chained member-count recovery prevents a failed prerequisite from becoming a permanent loading state.
by Steve Larson
Succeeded
30517
04471fd9 Fixed the editor's current-user read redirecting on an expired session The recipient count reads the current user as well as the count, and mounts its own observer of that query at every call site — so any step transition in the publish flow can refetch `/users/me/` and, on a 401, replace the page with the writer's unsaved work still in it. The redirect opt-out is also per fetch initiator rather than per cache entry, so a component outside the flow sharing one of its query keys can start a redirect-capable refetch of the same data. `useCurrentUser` now takes the same optional transport options the other hooks do, `useMembersCount` forwards its caller's options to both requests it makes, and the editor's status line opts its shared count and settings reads out too. `useMembersCount` also resolves a failed request to a null count rather than zero. Callers already render descriptive copy for null, so an unreadable count now reads "sent to all members" instead of claiming an audience of none, and the publish machine no longer sees a failed count as a site with no members.
by Steve Larson
Succeeded
30517
04471fd9 Fixed the editor's current-user read redirecting on an expired session The recipient count reads the current user as well as the count, and mounts its own observer of that query at every call site — so any step transition in the publish flow can refetch `/users/me/` and, on a 401, replace the page with the writer's unsaved work still in it. The redirect opt-out is also per fetch initiator rather than per cache entry, so a component outside the flow sharing one of its query keys can start a redirect-capable refetch of the same data. `useCurrentUser` now takes the same optional transport options the other hooks do, `useMembersCount` forwards its caller's options to both requests it makes, and the editor's status line opts its shared count and settings reads out too. `useMembersCount` also resolves a failed request to a null count rather than zero. Callers already render descriptive copy for null, so an unreadable count now reads "sent to all members" instead of claiming an audience of none, and the publish machine no longer sees a failed count as a site with no members.
by Steve Larson
Succeeded
30517
daf3a401 Changed every publish-flow request to opt out of the session-expiry redirect The editor's publish flow runs over a post that may still hold unsaved work, so a 401 on any request it owns must surface in the modal rather than replace the page. Its own reads already opted out; the recipient counts, the newsletter, tier and label queries, and the email retry did not, because those hooks had no way to carry transport options when the flow was written. `useMembersCount` now takes an options argument it forwards to the count query, and `useRetryEmail` maps a `sessionExpiryRedirect` flag off its payload the way the post mutations do. Both default to the previous behaviour, so other callers are unaffected. `useCurrentUser` stays redirect-capable: every screen shares it as a boot read, and it is not the flow's to opt out.
by Steve Larson
Succeeded
30517
daf3a401 Changed every publish-flow request to opt out of the session-expiry redirect The editor's publish flow runs over a post that may still hold unsaved work, so a 401 on any request it owns must surface in the modal rather than replace the page. Its own reads already opted out; the recipient counts, the newsletter, tier and label queries, and the email retry did not, because those hooks had no way to carry transport options when the flow was written. `useMembersCount` now takes an options argument it forwards to the count query, and `useRetryEmail` maps a `sessionExpiryRedirect` flag off its payload the way the post mutations do. Both default to the previous behaviour, so other callers are unaffected. `useCurrentUser` stays redirect-capable: every screen shares it as a boot read, and it is not the flow's to opt out.
by Steve Larson