Scheduled Trigger is out of beta and live for all customers. Distro routers can now run on a recurrence, on a specific date, or on demand. A Records for Processing node fetches the records to route using a SOQL query you define.
What's new since beta:
- Visual SOQL builder. Set conditions with a familiar UI instead of writing raw SOQL (raw SOQL is still available if you prefer it)
- 2,000-record cap removed. Each run was previously capped at 2,000 matched records. It's no longer capped.
A note on record volumes: even with the cap removed, run smaller batches where possible. Split large jobs into multiple narrower queries, and schedule outside business hours or over the weekend to minimize disruption to live routing.
Trigger types available:
- Recurring Schedule – e.g. every day at 8am.
- Specific Date – one-off run at a chosen time in the future.
- On Demand – kick off a run whenever you like. Also callable via the Edge API and MCP (resource-scheduler-run), so you can trigger a routing job from an external workflow, an AI agent, or an automation tool.
Check out the support article for more information.