Skip to main content

Scheduled

Use the Scheduled trigger to run a flow on a recurring cadence. There is no event source — the trigger is wired to a Job Queue Entry that AutoFlow creates when the flow is published, and every Job Queue run starts a fresh execution.

Typical examples include:

  • Generating a daily report and emailing it to a distribution list.
  • Polling an external API every few minutes and reacting to changes.
  • Running an end-of-day reconciliation across customers, orders, or warehouse entries.

What happens when the flow runs​

  1. When the flow is published, AutoFlow creates a Job Queue Entry that owns the schedule. The default cadence is every 60 minutes.
  2. Each time the Job Queue fires the entry, AutoFlow starts a new execution.
  3. The flow runs through its steps without any trigger payload — there are no outputs to consume.

Because the schedule lives on the Job Queue Entry, you change the cadence the same way you would for any standard BC job: open the linked Job Queue Entry and edit Earliest Start Date/Time, No. of Minutes between Runs, Recurring Job, and the day flags. Pausing the Job Queue Entry stops the schedule without unpublishing the flow.

Configure the trigger​

There is nothing to configure on the trigger itself. Selecting On a schedule shows a confirmation message ("There is nothing to configure for this trigger.") and the trigger is valid immediately. The scheduling parameters live on the Job Queue Entry that AutoFlow generates at publish time.

The Scheduled trigger produces no outputs. Read whatever data the flow needs from records or external systems in the first action steps.

Best practices​

  • Tune the cadence on the Job Queue Entry. The default 60-minute interval is a starting point, not a recommendation — drop it when you need higher frequency, raise it when downstream cost matters.
  • Keep scheduled flows idempotent. A run that misses or overlaps must not produce duplicates; gate work with a Decision step that checks "already done?" before mutating data.
  • Watch the execution log. Scheduled flows fire silently — without monitoring, a hung Job Queue Entry can pause your automation for days. Add the Job Queue Entry to your standard ops checks.
  • Use Manual instead for one-offs. A flow that you only run "once in a while when something happens" is a Manual flow, not a Scheduled flow with the cadence set very high.