History and settings

It is possible to see a list of automation runs for your published apps.
To do so, click the Settings tab in the app builder.

This will take you to the app overview screen where you can click on the Automations tab to see a list of your automation runs.

You can filter and order the logs by automation name, data range, and status.

There are three statuses:

• Success: The automation run was successful
• Stopped: The automation run was correctly terminated by a Condition
• Error: The automation run failed to complete due to an error
• Stopped - Error: Specific to Cron jobs. If the cron automation errors five times back-to-back, it will be disabled until you re-publish your app.

Investigating errors

Whenever an automation run errors, you will see a red banner at the top of your app list with the automation name and the number of times it failed in parentheses.

There is a convenient 'View error' link which will take you to the automation history, or you can click the 'X' to dismiss the notification.

When selecting an error, you will be able to see which automation step failed as well as the error output.

Furthermore, you can click the Edit automation button to be taken to the automation which may need fixed.

📘

Automation history will only show for published apps, and you must publish your app to apply any changes to your automations.

Expiration 🔒

Logs are kept for a single day on the free plan, but you can expand the duration of time that logs are kept significantly by upgrading.

Chain automations

On a per app basis, it is possible to toggle the Enable chaining setting on/off.

By default, this setting if off in cloud, and on in self-host.

When this setting is on, it allows any automation within the app that has any of the Row Triggers (Created, Updated, Deleted) to be triggered when another automation fires a Row action (Create, Update, Delete).

Whether to have this setting on or off depends on your use-case:

• If you want to restrict your automations to only trigger upon End User table writes, then toggle off.
• If you want your automation row triggers to fire when an End User OR an automation writes to a table, then toggle on.

Example

In this basic example, the first automation would only trigger then second if the Enable chaining toggle was on.

📘

Additional info

As it could be possible to accidentally get into an infinite loop, the maximum number of automations that can be triggered in a sequence is five.

Also, chaining automation row events should not be confused with the Trigger automation 🔒 action, which will always fire if used.