Automations only run if they are triggered in some way. There are different ways to do that:
1. Inside of miniExtensions:
Manually, by clicking the "run" button on our website.
Schedule it to run regularly using the Advanced options on the Run tab.
2. Outside of miniExtensions:
Trigger it with Airtable Automations (e.g. for any new record).
Trigger it by a Webhook. A Webhook is a unique URL for your automation that you call from another app (e.g. Zapier). Every time it’s fired (accessed), it will trigger the automation to run.
When triggered automatically, the automation will run in the same way as if you clicked on the run button on the settings page manually.
By default, many automations skip records that already contain data in their output field. To process those records again, select the Overwrite option where available, as explained here.
Scheduling Options
Schedule using miniExtensions
Choosing Run once per day in the Schedule settings makes the automation eligible to run immediately. After a successful scheduled run, record-processing automations become eligible again 24 hours after completion.
Run duration and queue delays can shift the start time, so Run once per day does not guarantee a fixed clock time each day.
To set this up, just go to
Your automation's Run settings
Advanced
Schedule
Select Run once per day
Schedule using Airtable
If you need to trigger an automation at a specific clock time, such as 4AM each day, you could use an Airtable automation to trigger it instead. Airtable's automations support setting a specific schedule to run, so you could set it to run at 4AM every day, and use a script to trigger your miniExtensions automation. This help article explains how to set this up!
Failed scheduled runs
If you'd like to be notified of any failed scheduled runs, make sure to turn on "Email on Failure" in the Schedule modal of your automation's configuration. Failure notifications go to the workspace owner and have a six-hour cooldown per automation. The schedule is disabled automatically after 30 consecutive failures counted by the scheduler; a successful scheduled run resets that counter.