Skip to main content

Scheduling Workflows

A schedule starts a new mission from a workflow at set times. Each workflow has at most one schedule, and it's controlled by the workflow's Trigger node.

Set up a schedule​

  1. Open the workflow in the builder and click its Trigger node.
  2. Set Trigger Type to Scheduled.
  3. Choose a Frequency and, if needed, a Start Date/Time or Cron Expression (see below).
  4. Click Save Changes.

Saving creates the schedule, or updates it if one exists. The workflow's status (Draft or Live) makes no difference — any workflow that isn't Archived runs on its schedule.

To pause scheduled runs, either set Trigger Type back to Manual and save, or turn off Active on the schedule (see Manage schedules).

Frequencies​

FrequencyWhen it runs
OnceOne run at Start Date/Time (or as soon as possible if that has passed or is blank). The schedule then switches itself off.
HourlyEvery hour.
DailyEvery 24 hours.
WeeklyEvery 7 days.
MonthlyOnce a month, on the same day of the month (days after the 28th move to the 28th).
Custom (Cron)Whenever the Cron Expression matches.

For Hourly, Daily, Weekly and Monthly, the first run is one full interval after the start time (or after you save, if the start time is blank or past), and each later run is one interval after the previous one. To run daily at a precise time, use Custom (Cron).

FYAI checks for due schedules about once a minute, so a run can start up to a minute or so after its time.

Times are UTC​

  • Cron expressions are evaluated in UTC.
  • The Start Date/Time you enter on the Trigger node is treated as UTC.
  • The Start Date/Time picker in Edit Schedule (on the Missions page) uses your browser's local time and converts it.

For example, 9:00 am New Zealand Standard Time (UTC+12) is 21:00 UTC the day before, so weekdays at 9 am NZST is 0 21 * * 0-4.

Cron expressions​

Five fields, separated by spaces:

┌───────────── minute (0–59)
│ ┌─────────── hour (0–23, UTC)
│ │ ┌───────── day of month (1–31)
│ │ │ ┌─────── month (1–12)
│ │ │ │ ┌───── day of week (0–6, Sunday = 0)
│ │ │ │ │
* * * * *
ExpressionRuns
0 9 * * 1-509:00 UTC, Monday to Friday
0 */4 * * *Every 4 hours, on the hour
30 8 1 * *08:30 UTC on the 1st of each month
0 0 * * 0Midnight UTC every Sunday

If an expression can't be read, the schedule falls back to running hourly. Check Next: on the schedule after saving.

What a scheduled run receives​

  • The run's initial message is "Scheduled execution".
  • Attribute values are empty — default values are not applied. Write the inputs directly into your nodes' input messages.
  • Scheduled runs appear in mission history and in the workflow's Executions with Trigger shown as Schedule.

Manage schedules​

  1. Go to Build → Missions.
  2. Under Recent runs, click View all history.
  3. Open the Scheduled tab.

Each schedule shows its workflow, frequency, Paused if it's switched off, Next: and Last: run times, and how many scheduled runs failed.

Click the pencil (Edit schedule) to change:

SettingDescription
FrequencyAs above.
Start Date/TimeLocal time. "When the schedule begins (leave blank to start immediately)".
Cron ExpressionFor Custom (Cron).
Execution EnvironmentThe execution environment for scheduled runs. "Leave blank to use the project default environment" (Project Default).
ActiveOff pauses the schedule without deleting it (and sets the Trigger node back to Manual).

Edits here are copied back into the workflow's Trigger node, so the builder and the schedule stay in step. Click the bin (Delete schedule) to remove a schedule entirely.

You can also manage schedules through the API (/workflow-schedules) or the Platform MCP server.

Tips​

  • Run it manually first from Missions and check the output before scheduling.
  • Add a Kill Switch after the Trigger so you can stop scheduled runs instantly, including one in progress.
  • Watch costs. Every scheduled run uses tokens. The workflow list shows each workflow's Avg Cost.
  • A deactivated (Archived) workflow never runs on its schedule.