Troubleshooting
A flow that never runs, missing devices, cooldown and busy, actions that fail, and reading Recent runs.
The flow never runs
- Is it published? A draft-only flow has no running graph. The banner says Not published yet.
- Is it enabled? Check the toggle in the header and the Flows list.
- Does it have a When step that is connected to the rest? Add a "When" step in the issues strip means nothing can start it.
- Does the trigger actually fire? Open the When step and look at its Now: reading. For Device changes, offline / online transitions do not count unless ticked; for sensors, a minimum change or for seconds setting may be filtering reports.
- Is the hub online? The status chip in the header.
A condition always takes "otherwise"
- Compare the Now: line on the step with what you expect, including units.
- An unknown state warning in the issues strip means the typed state is neither a raw token nor a label this device uses (a motion sensor is Detected / Clear, not Open); pick one of the values the warning lists.
- Time between and schedules use the home's time zone; check the location's address is set.
- Presence steps watch the household / person / place presence; a phone with location sharing off never arrives.
Missing device
The Flows list shows a Missing device badge when a step references a device the location no longer has (renamed devices keep their id; deleted or re-paired ones do not). Open the flow, fix the step the issues strip points at, and publish again.
"On cooldown" / "Already running"
Cooldown is a per-flow setting in the header menu. Already running means the hub's concurrent-run limit is reached; long Wait steps hold a slot each. Shorten waits or add Stop waiting before re-triggering.
An action fails but the flow continues
That is by design: a rejected service call (device offline, unsupported option) is logged and the walk continues. Look at Recent runs and, with debug mode on, the Messages panel for the reason. Add an And › Device is check before the action if a failure should stop the run.
Reading Recent runs
Each entry shows the trigger, the outcome, and Log step messages. A run that ended at a Stop step is still "ok" and shows where it stopped. Use Log steps generously while developing and switch them to Debug message when done.
Still stuck
Export the flow (Flows list → Export), note the hub status, and share both with support.