What it is
An engine state is one word for whether an engine has run for you and how current its figures are: Running, Late, Stale, Partial, Failed, Not measured, Nothing yet, Not on your plan, Paused, Not on the run. There are eight states behind those words. An engine that is fresh prints no word at all: its as-of carries the time and nothing else needs saying. An engine that has never run prints no word either, and one sentence. Every engine derives its state by one rule, so the word means the same thing on every page, in the Inbox, and in an answer from Ask Tightly.
How Tightly decides it
The state is worked out, never stored, from the newest run record and the engine's own clock: how often it is expected, how old its figures may be before they are Late, how old before they are Stale, and how long one run may take.
A run in flight inside its bound is Running. A run that finished and whose figures are younger than the late threshold is fresh. Past that threshold the engine is Late; past the stale threshold it is Stale. A run that finished but left some rows unwritten is Partial: the page keeps both dates and never blends them. A run that did not finish, while the previous good run is still inside the stale threshold, is Failed; once that too is past, the engine reads Stale with the failure as its reason. A run that was skipped because nothing was promised prints the reason's word: Nothing yet where there was nothing to compute from, Not on your plan where the plan does not include the engine, Paused where the connection is paused, Not on the run where your tenant is not on that engine's run. A skipped run that left the promise standing, a duplicate dispatch, a run that was not due, a step cut off upstream, a night held by staff, is stepped over, and the state comes from the run beneath it.
The clocks come from the schedules the platform already keeps. Your sales are Late three hours after their last sync and Stale after eight. Every engine that runs with the sync is Late at four hours and Stale at twenty-six. The weekly verdicts are Late at 06:00 UTC on Monday and Stale at 06:00 UTC on Tuesday. A page that shows figures with no run record behind them yet reads Late with no date and no sentence until the next run: the platform will not claim a time it cannot prove. An engine whose runs the platform does not record yet, such as the Monday re-score, the accuracy pass and the analog run, reads Not measured with no date, rather than claiming it never ran.
The words on the face
| Word | When | What the page does |
|---|---|---|
| none | fresh | The as-of alone: Sep 4, 2026 · 6:05 AM |
| Running | a run is in flight | The last run's as-of gains the engine's clause, such as recomputing now; the buy and the verdicts say a sentence instead |
| Late | past the late threshold | The as-of gains the word late; nothing else changes and nobody is told |
| Stale | past the stale threshold | The as-of gains stale, the page prints its one state sentence, one Inbox row and one email |
| Partial | some rows are older | The sentence names what was and was not rewritten; each row keeps its own date |
| Failed | the last run did not finish | The as-of gains the last run did not finish; the sentence names the date the figures are from; one Inbox row |
| Nothing yet · Not on your plan · Paused · Not on the run | skipped, nothing promised | The sentence; no as-of; no Inbox row |
| Not measured | no run record is kept for it | The word, no as-of |
| none | never ran | One sentence, no as-of |
Failed, Paused and Not on your plan are the Integrations page's own words, so a sync and an engine read alike. No colour and no dot carries any of these: a late engine is a fact about the platform, not a declared promise at risk. When the state itself could not be read, the figures keep their own stamps and the as-of line reads engine state not read, which is never the same claim as a run that failed.
What you can do about it
Late asks nothing of you; the next run is already due. Stale, Partial or Failed on the forecast offers Recalculate now under Forecast status in the Forecast performance drawer on Demand forecasting, once every two hours. Paused offers Integrations, where the connection is resumed. Every other engine retries on its own, and the Inbox row closes itself when the run recovers. The sentences themselves, engine by engine, are in What each engine says, state by state; staff read the same rows with the error behind them, described in The health read.
Glossary line
Running, Late, Stale, Failed, Nothing yet, Not on your plan, Paused, Not on the run.