Skip to main content

Find out why an automation failed

An automation reads Failing when its last run failed, one of its targets failed, or Jaah stopped it. Until you fix the cause it keeps failing, and its tasks are not filed. Your organization's Owners and Admins are told when one keeps failing. This guide takes you from the alert to the cause.

Who can do this: requires the org admin role. Automations are listed under Audit, which only Org Owners and Admins see.

  1. In the sidebar, select Audit, then the Automations tab.

  2. Set Status to Failing. Each failing automation has a cross before its name. Hover a row to read why it fails.

    Audit, Automations with Status set to Failing: three automations with a cross before each, two marked Owner no longer in this org

  3. Select the automation's name. Its page opens beside the list. Under the name, Failing is followed by the cause in red, and the full text of the last failure under it.

    An automation's page: Failing, the cause naming the deleted Invoicing project, the last run's full text, and Run now, Pause and Delete

  4. Select the Runs tab. Runs are listed newest first; a failed run's line is red and starts with what went wrong. To leave out runs that only skipped, set Status to Hide skips.

    The Runs tab: three red runs that failed on a deleted project, then older runs that filed tasks

  5. Select the failed run, or Open in its ⋯ menu. Under Targets, Error comes first, listing each project or node that failed and why. A run with no targets listed says what happened under This run.

  6. Fix the cause the run names. Common ones:

  7. Select Run now at the top of the page, then open Runs again. A good run clears Failing. If Jaah stopped the automation, select Resume as well.