Why an automation didn't run

Troubleshooting · Audience: tenant-admin · Permissions: automation.logs.view

How to check an automation's execution history and diagnose why it didn't fire or didn't do what you expected.

What this does

Explains where to check what an automation actually did.

Who can do this

Anyone with automation log-viewing permission.

What happens next

Every automation keeps an execution log with one of three results — success, skipped (the condition filter didn't match), or error (the action itself failed, with the real error message). Check first whether the automation is Active — an inactive one never runs regardless of its trigger. Then check that the event you expected really matches the trigger type exactly, and that any condition you added isn't narrower than intended.

Troubleshooting

• The automation never appears to have run at all — confirm it's Active, and that the exact trigger event actually occurred. For Task Overdue specifically, this is detected by a periodic background check, not instantly.

• The log shows "skipped" — the condition filter didn't match for that event.

• The log shows "error" — read the exact error message; a common cause for Assign Onboarding Template or Assign Asset is a wrong/stale ID, or (for an asset) the asset no longer being "available." A failed run does not automatically retry.

• It ran but took the wrong action, or you need to change what it does — there is no edit screen for an existing rule; delete it and create a new one.