Scheduled Recipe Runs Only Every 60 Minutes Instead of 30 Minutes

There are scenarios in which a Recipe configured to run “every 30 minutes” is executing only once every 60 minutes. The scheduler shows the next run as 60 minutes away, and there is no run attempt or failure at the 30-minute mark.

For example, a CRM Analytics recipe scheduled to refresh an opportunity pipeline dashboard every 30 minutes may appear to only run at the top of each hour if the start time is set to :30 instead of :00.

This happens because the system uses a cron-style matching scheduler, not an interval-based timer. The scheduler checks the current minute and runs the job only when the current minute matches the cron pattern. It does not track when the job last ran or calculate “30 minutes after the previous execution.”

Because of this design:

• The scheduler is matching-based, not interval-based.

• It does not remember the last run time.

• It does not compute actual elapsed intervals.

• It simply checks whether the current minute is part of a predefined set of valid minutes.

Because of this model, repeating intervals must align with minute 0 of the hour and must divide evenly into 60. For example, you can express the time as Cron Expressions like:

• Every 10 minutes → */10 → :00, :10, :20, :30, :40, :50

• Every 15 minutes → */15 → :00, :15, :30, :45

• Every 20 minutes → */20 → :00, :20, :40

• Every 30 minutes → */30 → :00, :30