Logic Composer

Schedules

Run a logic flow on a recurring timetable, in the time zone you choose, with runs you can predict.

A schedule runs a logic flow at regular intervals without anyone triggering it: every five minutes, every morning at 06:00, every Monday, or on the first of each month. Use schedules for periodic work such as SLA checks, nightly clean-ups, reminders and month-end processing.

Create a schedule

Go to Logic FabricSettingsSchedules and select New.
Enter a Name and choose the Project.
Choose the Logic Flow to run. It is locked after the first save.
Set the Frequency and Interval, for example Day and 1 for every day.
Set the Start Date: the date and time of the first run. Later runs keep this time of day.
Check the Time Zone. It defaults to your own time zone.
Save the form. Next Run Date shows when the flow runs next.

Settings

Setting	What it does	Notes
Name	Identifies the schedule	Locked after the first save
Project	The project the schedule belongs to	Locked after the first save
Logic Flow	The flow that runs	Locked after the first save. A flow that a schedule uses cannot be deleted. The flow runs with no inputs: choose a flow without required inputs, or every run fails. Optional inputs are empty.
Frequency	The unit of the interval: Minute, Hour, Day, Week or Month
Interval	How many units between runs	Hour and `4` runs every four hours
Start Date	The first run, and the anchor for every later run
Time Zone	“The time zone the schedule runs in. Daily, weekly and monthly runs keep the start time of day in this time zone, including across daylight saving changes.”	Defaults to the time zone of the user who creates the schedule
Next Run Date	When the flow runs next	Read-only
Last Run Date	When the flow last ran	Read-only
Status / Status Reason	Active (Started) or Inactive (Stopped)	Deactivate the schedule to stop it; activate it to start it again

What you can rely on

Runs are anchored to the Start Date. Every run is counted from the Start Date, never from when the previous run actually happened. A schedule therefore does not drift, even when a run starts late or takes a long time.

Minute and Hour schedules use elapsed time. An hourly schedule runs every 60 minutes, regardless of the clock or daylight saving.

Day, Week and Month schedules keep the time of day of the Start Date in the schedule’s Time Zone. A daily 09:00 run stays at 09:00 local time in summer and in winter.

Months are calendar months. A monthly schedule that starts on the 15th runs on the 15th of every month. A schedule that starts on the 31st runs on the last day of shorter months, such as 30 April or 28 February.

Daylight saving changes are handled for you:

When clocks go forward and the run time does not exist that day (for example 02:30), the run happens at the equivalent time after the change.
When clocks go back and the run time occurs twice, the flow runs once, at the first occurrence.

Missed runs are not piled up:

If runs were missed because a run was delayed or still running, they are combined into one run, and the schedule continues at the next future time.
Runs missed while the schedule was deactivated are skipped. When you activate it again, it runs at the next time on its Start Date timetable.

Changing the Start Date or Time Zone reschedules the next run straight away.

When a run fails

Each run happens in the background, with no surrounding transaction: changes the flow saved before a failure are kept. The schedule keeps planning its next runs after a failed run.

A run that ends with Raise Error is recorded as a successful run. When a scheduled flow needs to report a problem, record it before Raise Error, for example by creating a note or a log row that your team reviews.

Example: SLA monitor and month-end invoicing

A service team needs two automated jobs in Dubai:

Schedule	Logic Flow	Frequency	Interval	Start Date	Time Zone
`SLA monitor`	`Check SLA breaches`	Minute	`5`	today, 00:00	Gulf time (UTC+04:00)
`Monthly invoicing`	`Generate monthly invoices`	Month	`1`	1 February, 01:00	Gulf time (UTC+04:00)

The SLA monitor runs every five minutes and flags cases that are close to breaching. The invoicing schedule runs at 01:00 local time on the first day of every month, so each run covers exactly one calendar month.

For a European team, a daily report scheduled for 06:00 with a Central European time zone keeps running at 06:00 local time after the switch to summer time.