Skip to main content

Fix an automation that didn't run or failed

Check status, trigger filters, and run history when an automation doesn't run or a run fails.

Written by Max Sherman

Who can do this: Administrators and Meeting Managers.

Start with the run history

Select Automations in the sidebar, open the automation, and scroll to Run history.

  • If there's no run for the event you expected, the trigger didn't match. See the next section.

  • If the run Failed, expand it. The failed step shows the error, and Open Ava conversation shows the full story of the run.

The automation didn't run

  • It isn't Active. Draft and Paused automations don't run on their own. Select Activate.

  • A filter didn't match. Check Meeting types on the trigger. For Document generated, each entry in Document kinds must match the whole kind name. For Document added, check File name contains.

  • The meeting wasn't ended as a live meeting. Meeting ended runs only when a live meeting is ended in ClerkDirect. For any other meeting, use Run now and choose the meeting.

  • It's too soon. Runs for Document added start about three minutes after the upload.

  • The schedule hasn't come round yet. Scheduled runs happen on the hour, in the automation's time zone. Activating or saving an automation doesn't create runs for dates that have already passed; the first run is the next scheduled time. Next run on the Automations list shows when that is.

  • An automation started it. An automation's own work never triggers the same automation again, and a chain of automations triggering each other stops after three.

A run failed

  • "The member this run acts as is no longer in the organization." (or "The member this action runs as…") The person the run acts as has left the workspace. Choose a current member as the Default owner, or update the meeting's owner, then run it again.

  • "Only meeting managers or administrators can request reviews." The member the run acts as is a Participant. Choose an Administrator or Meeting Manager as the Default owner or meeting owner.

  • "Choose at least one reviewer." Add Reviewers to the Request review step.

  • "No document is available for this step." A Request review or Copy to SharePoint step had no document to work on. Put a Generate document with Ava step before it, or use a document trigger.

  • "SharePoint is not connected" or "Configure a SharePoint destination before exporting this file". An Administrator needs to connect SharePoint and choose a folder in Workspace settings, under Integrations.

  • A step "timed out". The step waited more than 24 hours, for example for a transcription. Check the meeting's recordings, then use Run now.

  • "The run was canceled while Ava was working." Someone selected Stop run.

The run completed, but something is missing

  • Some tasks weren't created. People who have left the workspace are skipped. The step summary says how many.

  • Ava didn't create a document or task. Open the run's Ava conversation. Ava ends each step with a report of what it created and what it couldn't do, for example because a session had nothing to draft from. Make the step's Prompt more specific, then run it again.

  • A reminder didn't post. Remind about open tasks only comments on open tasks created by the automation chosen under Tasks created by. Tasks marked Done or Canceled aren't reminded.

Run it again

After you fix the problem, save the automation and select Run now. For a scheduled automation, running a Create tasks step again on the same day doesn't duplicate the tasks it already created for that day.

Related articles

Did this answer your question?