Scheduling

Workflows can run on a recurring schedule. Add a schedule object to the workflow definition.

Configuration

{
  "name": "daily_reconciliation",
  "definition": {
    "schedule": {
      "every": "1d",
      "at": "02:00",
      "timezone": "America/New_York"
    },
    "actions": [ ]
  }
}

Schedule Fields

Examples

Daily at 2:00 AM Eastern:

{
  "schedule": {
    "every": "1d",
    "at": "02:00",
    "timezone": "America/New_York"
  }
}

Every 6 hours:

{
  "schedule": {
    "every": "6h"
  }
}

Every 30 minutes:

{
  "schedule": {
    "every": "30m"
  }
}

Weekly (every 7 days) at midnight UTC:

{
  "schedule": {
    "every": "7d",
    "at": "00:00"
  }
}

How Scheduled Runs Work

Scheduled workflows execute with an empty @input unless a default input payload is configured. The @now context variable reflects the timestamp at execution time.

Each scheduled occurrence creates a standard workflow run with its own run_id, context, and audit trail. It follows the same execution path as a manually triggered run.

Scheduled occurrences are independent. Design side-effecting steps to be idempotent when a schedule can fire again before earlier work has finished.