tr
TryGhost
GitHub
Ghost
Workspace
GitHub
CI Pipeline Executions
Current execution
Failed
troy-ny-1558-addendum-admin
Runs and Agents
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Changed the Tinybird sync cadence back to every five minutes ref https://linear.app/ghost/issue/NY-1559 The job was moved to a 20-second cadence for local development so a change in the automation tables showed up in Tinybird quickly. That cadence is far more than the stats need, and it removed all slack from the pipeline: a run that failed was retried 20 seconds later with no backoff, and a run that outlasted the interval meant the next tick attached to it immediately, so any backlog was sent as one continuous stream. Five minutes is the cadence the job was designed for, matches the other recurring maintenance jobs, and is a natural retry delay after a failed run. The random per-process offset stays so sites do not all run at once.
nx run ghost-monorepo:lint:boundaries
⌘K
Succeeded
nx run ghost-monorepo:lint:boundaries
Click to copy
Linux
4 CPU cores
read-write
access token used
9bedc1ab
30560
GitHub
Ghost
Workspace