Jobs and Schedules

A job is a catch-all term for the flows and services that can be scheduled. A schedule is a rule that dictates when and how often specific jobs should execute.

You can manage both jobs and schedules from a workspace's Jobs icon Jobs tab. The two are grouped together so you can move from creation to execution seamlessly.

A workspace's Jobs icon Jobs tab is slightly different depending on whether it is part of an Integration or an Automation workspace, but both pages enable you to manage the schedules that run jobs and services. For context-specific explanation of each Jobs icon Jobs page, see:

There are two types of schedules, each with their own logic that persists across both automation and integration workspaces: interval-based scheduling and chronological scheduling.

  • Interval-based scheduling is the default. Use it to run a schedule repeatedly on a fixed cadence (for example, every 15 minutes or every 2 days) without pinning it to specific calendar days or times. This means while the shorthand description might say every day at 2pm, this will vary with daylight savings time.

  • Chronological scheduling lets you pin a schedule to specific days of the week or month and a specific time — for example, "every Monday and Wednesday at 4:00 AM" or "the first Monday of every month." Use it instead of interval-based scheduling when the timing needs to line up with the calendar rather than a fixed repeating cadence.

General Scheduling Logic

Both interval-based and chronological scheduling adhere to some general logic. Keep this in mind when setting and managing schedules.

  • A schedule's actual start time is determined by the moment the schedule is created or activated in a specific workspace.

  • To protect client-specific needs, local edits to a schedule are persistent. If you modify a schedule's cadence in a customer workspace, those specific fields are no longer overwritten by global integration syncs.

  • When a schedule is first activated, the interval decreased, or if the start time is moved back, the system automatically identifies schedule as behind and instantly runs its jobs to catch up.

  • Updating the jobs within a schedule does not force an immediate run. Modified jobs will execute during the next naturally scheduled interval.

Scheduling Best Practices

  • Prevent Data Collisions: Stagger schedules so they never access the same data at the same time to avoid database locks.
  • Buffer for Cache Writes: Set start times further apart than the duration of your longest cache write to ensure data is fully committed.
  • Sequence Related Tasks: Group dependent tasks into a single schedule to force them to run in the correct order.
  • Separate Management Types: Keep managed and unmanaged schedules in separate workspaces to avoid logic conflicts.
  • Prioritize Schedules over Manual Runs: Prefer schedules for production tasks. They have built-in protections against concurrent writer errors that manual runs lack.
  • Isolate Large Data Loads: Use dedicated schedules for large initial data loads to prevent long run times from delaying routine operations.