Skip to main content
Workflows can run on a schedule using cron expressions defined in schedules.json. The platform registers schedules during deployment and triggers workflow submissions automatically.

Configuration

Define schedules in schedules.json at the root of your app:

Common cron expressions

Preventing overlapping runs

Set skipIfRunning: true to avoid starting a new run when the previous one hasn’t finished. This is recommended for long-running workflows where concurrent execution could cause data conflicts or duplicate processing.

Build-time validation

The app framework’s build pipeline validates schedules.json during the build phase:
  • Cron expressions are syntactically valid
  • Workflow file paths resolve to exported workflow definitions
  • Parameter values match the workflow’s variable definitions
  • Schedule names are unique

Manual triggers

Scheduled workflows can also be triggered manually through the app’s API or UI. The same workflow definition is used — only the submission source differs (scheduled vs. manual).