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 tab. The two are grouped together so you can
move from creation to execution seamlessly.
A workspace's 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 page, see:
Regardless of the workspace type, schedules globally follow the same logic.
Schedule Logic
-
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.
-
Schedules are calculated based on time elapsed since the last run, rather than a fixed "wall clock" time. This means while the shorthand description might say every day at 2pm, this will vary with daylight savings time.
