Skip to main content

Automation executions: monitor runs, statuses, and export reports

See the status of each automation execution and open its details. You can also export the executions report to Excel for further review.

Automation executions: monitor runs, statuses, and export reports

See the statistics on the Automations list, check the status of each run, open its step-by-step details, and export a report to Excel.

Where do I see automation activity?

The top of the Automations list shows execution statistics for your organization, including total trigger executions over time and the most executed triggers. To see a single automation's history, open it and go to the Executions section.

How do I read execution statuses?

Each execution row shows the user, the run date, and the current status. The statuses you may see are:

  • Scheduled: the run is planned for a later time, for example while it waits on a Delay step or an onboarding delay.

  • Pending: the run has started but no step has begun yet.

  • Running / In Progress / Processing: the pipeline is currently executing.

  • Completed: all steps finished successfully.

  • Error / Failed: a step could not complete.

  • Canceled: the run was stopped.

  • Skipped and Unknown: a step was not run, or the status could not be determined.

What details can I see for a run?

Select View Details on a run to open its Execution Pipeline. It shows the user, the triggered, scheduled, started, and completed times, the current step, and the status of every step.

When a step finishes, the details show what was delivered: for an email, the recipient, subject, and body; for a push notification, the recipient, title, and body.

How do I export the report?

From a row in the Automations list, select Export to download that automation's report. The export is an XLS file containing the rows available for that automation, which is useful for reviewing runs outside GFoundry or sharing them with your team.

Why is an automation not running?

First, check that it is Enabled in Automation Details. A disabled automation is never triggered. If it is enabled but you see no runs, confirm that the trigger's precondition matches the users you expect, and remember that runs with a Delay step or an onboarding delay appear as Scheduled until their time arrives.

Did this answer your question?