What a Scheduler Does
When a scheduler fires, it runs the Route it is attached to. This means both the Incoming and the Outgoing parts of the route are executed, in that order. For the available scheduler types and their configuration options, see the Schedulers reference.Multiple Schedulers for Parallel Processing
A Route can have more than one scheduler. When you combine this with the Enable parallel processing option on the Route, each Scheduler runs as one parallel process. For the trade-offs, see the parallel processing option on the Routes page.Other Ways to Trigger a Route
A Scheduler is not the only way to run a route:- Real-time processing on the route runs the Outgoing automatically as soon as a task is created. See the route options.
- A Webhook can inject data directly into the Incoming configuration, creating tasks without waiting for a Scheduler.
Repairing stuck Tasks via Scheduler
Tasks occasionally get stuck in a Processing status when an integration process is interrupted before it completes. Left unresolved, stuck Tasks block the queue and prevent new data from being processed. The Repair stuck tasks Scheduler job detects these Tasks automatically and resets them so processing can resume.Setting up the Repair stuck tasks Scheduler
Navigate to Integrations > Schedulers and create a new Scheduler. In the Job dropdown, select Repair stuck tasks. Three configuration options appear below the Job field: Minimum age of tasksDefines how long a Task must have been stuck in Processing status before the Scheduler attempts to repair it. Set the Number field to a value and select the Unit (minutes, hours, or days). This prevents the Scheduler from prematurely interfering with Tasks that are simply taking longer than usual to complete. Routes
Limits the repair job to specific Routes. Select one or more Routes from the dropdown to check only those, or leave the field empty to check all Routes in the environment. New task status
The status to assign to a repaired Task. Three options are available:
- New –– resets the Task so it will be picked up and processed again on the next Route run.
- Failed –– marks the Task as failed for manual review.
- Skipped –– excludes the Task from further processing.
Set up this Scheduler proactively on all environments. Stuck Tasks are not always immediately visible and can silently block a queue for extended periods if not caught early.