Trace
Capture a screenshot or summary of the automation trace.
Home Assistant automation did not run
Use this flow when a Home Assistant automation did not fire or complete. It starts with the trace so you can separate trigger failure, condition failure, and action failure.
Safety first: be careful when testing automations that control locks,
garage doors, heaters, pumps, or other safety-sensitive systems.
What this flow is for
The automation did not run as expected, but it is still unclear whether the trigger failed, a condition blocked the run, or an action or integration failed.
First safe checks
- Open the trace first instead of the logs blindly.
- Ask whether the trigger fired.
- Ask whether a condition failed.
- If the action failed, isolate the failing action instead of editing everything at once.
Evidence requests
Ask for the best evidence first
Automation shape
Summarize the trigger, condition, and action path.
Entity status
Note whether any related entities were unavailable or stale when the run should have happened.
Likely causes
Most likely problem buckets
Trigger failure
The automation never started because the trigger did not fire.
Condition failure
A condition blocked the run even though the trigger fired.
Action or integration failure
The run reached the action stage but failed because a device, entity, or integration was unavailable.
Logic mismatch
Time zone, schedule windows, or templates no longer match the intended behavior.
Next safe steps
Take one step at a time
ACT-AUTO-002
Check the trace first so you know whether the trigger, condition, or action failed.
ACT-AUTO-004
If the trigger fired, identify the exact condition or action that stopped the run.
ACT-AUTO-005
Review time zone, schedule windows, templates, and entity availability only after the trace is clear.
ACT-AUTO-003
Reload the affected integration only after you capture useful evidence.
Best follow-up ask
What does the trace show: did the trigger fire, did a condition fail, or did the action fail?
When to stop and hand off
Escalate when the issue requires integration-specific logs, complex template debugging, or a broader redesign of the automation logic.
Support links
Follow the symptom that shows up next
If the automation trace points to unavailable entities or the setup feels bigger than one failing rule, move into the closest recovery or onboarding page next.
Open device-offline guide Open onboarding and recovery path