Project health
One state per project, every problem with what is wrong, why it matters and how to fix it, and when a workflow counts as tested.
Updated October 8, 2026 · 2 min read
The states
A project shows one state, the first that applies:
| State | When |
|---|---|
| Blocked | Something stops a Live run: a workflow error, Claude not connected or refused, saved credentials unavailable, or the plan's Live runs used up. |
| Error | Its runs keep failing: many failures in the last 7 days, or the same error three times in a row. |
| Not configured | It has no workflow, or only empty ones. |
| Running | A Live run is in progress. |
| Testing | A Simulation or a test run is in progress. |
| Needs attention | Any other problem. |
| Ready | No problems, and every workflow tested as it is now. |
Running and Testing don't hide problems: the count stays next to them. Project health isn't the same as a workflow's health in tables, which only reads its recent runs.
Problems and fixes
Each problem says what is wrong, why it matters (naming the step it affects) and offers one fix, such as Connect, Reconnect, Open workflow, Add Capability or Run a test. A fix opens the page where the change happens, and that page asks before changing anything. A fix your role can't make is shown disabled, with the reason.
When a workflow is tested
- Tested: a Live run of its current version succeeded.
- Simulated only: only a Simulation succeeded. Simulation never reaches your connected services, so run a Live test.
- Changed since its test: you edited it after the last successful run. Moving nodes on the Canvas doesn't count as a change; editing an instruction does.
Before a Live run
On the Canvas, a workflow in a project shows its project's state in the run panel, with Review & Fix when something is missing. It's a recommendation: Run stays available.
What is kept
Health is worked out when you look, from what the platform already keeps: workflow definitions, connection states, and runs' outcomes, error codes and a fingerprint of the version that ran (never its content). Each change of state is recorded in the activity log, with the problems' codes.