For the complete documentation index, see llms.txt. This page is also available as Markdown.

Run history and activity log

Check what your automations did, when each run happened, and why a run failed or was skipped.

Every time an automation runs, Loopit records what triggered it, each action it took and the outcome. You can see this for all automations in the Activity log, or for one automation in its Run History tab.


View the activity log

1

Open it

Go to Automations and select Activity log.

2

Read Recent runs

Each row is one action, newest first, 20 per page. It shows When it ran (as time ago), the Automation, its Type, the Action, the Outcome (that action's status) and the Time saved.

The Recent runs list in the activity log
3

Change the view

Use Previous and Next to move between pages, and the date range at the top to see a different period.


View an automation's Run History

1

Open the tab

Open the automation and select the Run History tab.

2

Read each run

Each row shows the record that triggered the run, the Customer, when it Started At, how long it took, the version that ran, its Progress and Status.

If a run failed, the Comment column explains why.

3

Expand a run

Select the arrow next to a run to see each action in it: who it was sent to (Recipient), when it started, when it was Scheduled for (for actions after a Wait), when it ended and its status.

Run History with a run expanded to show its actions
4

Search, filter and refresh

Type in Search trigger or customer to find a run by its record, such as an invoice number, or by customer name. Use the Status filter to show only failed runs, for example, and Refresh to load the latest runs.


What each outcome means

Outcome
Meaning

Completed

Every action ran.

Scheduled / Pending

The run is waiting, usually behind a Wait action.

Running

The run is in progress.

Skipped

The action didn't run. Common reasons: the conditions were no longer true after a Wait (or before a delayed SMS), the scheduled step was cancelled, no recipient or template was found, or, for a payment-failed SMS, the invoice was already paid.

Failed

An error stopped the action, for example the email provider rejected the message. Check the Comment for the reason. A missing recipient or template marks the action Skipped, not Failed.

Cancelled

The run was stopped before it finished.


Important things to note

  • Times in Run History are shown in your workspace's time zone.

  • Select the failed runs count on the Overview tab to jump to the failed runs in the activity log.

Last updated