Schedules and Run now
How often a connection runs, why every time is in UTC, and running one on demand.
Who can do thisWorkspace Administrator
Every connection has a trigger. It either runs on a schedule, or it only runs when someone clicks Run now. This article covers the schedule picker, why every time in it is UTC, and running a connection on demand.
The Integration Hub is in English only, so its labels are quoted in English in the Danish articles too.
Choose a trigger
The schedule lives in the Schedule & status section of the connection's editor. Open it from ConnectionsEdit on the row, or from Edit on the connection's page.
- Trigger: On a schedule or Manual (Run now only). A new shared mailbox starts on On a schedule with Hourly. A new Intune, Jamf Pro or REST connection starts on Manual (Run now only); when you switch it to a schedule, it suggests daily at 02:00 UTC.
- Enabled: off by default for every new connection. A schedule only runs while the connection is enabled, so remember to switch it on before you Save.
The Webmercs vendor connection has no schedule at all. Its trigger is On approval: Flexshop sends each fully approved request when it happens.
The schedule picker
With On a schedule chosen, the picker shows a Frequency list, the fields that frequency needs, a plain sentence describing the schedule and a Next: preview of the coming runs.
| Frequency | Extra fields | Default when you pick it |
|---|---|---|
| Every minute, Every 2 minutes, Every 5 minutes | None. Shared mailboxes only. | Not used as a default |
| Every 15 minutes, Every 30 minutes | None | Every 15 minutes |
| Hourly | None. Runs on the hour. | Every hour |
| Every few hours | Every N hours: 2, 3, 4, 6, 8 or 12 | Every 4 hours |
| Daily | Time (UTC) | 02:00 UTC |
| Weekly | Day and Time (UTC) | Monday 09:00 UTC |
| Monthly | Day of month (1 to 28) and Time (UTC) | Day 1, 02:00 UTC |
| Advanced (cron) | Cron (UTC): a five-field cron expression | The cron for whatever you had chosen |
Below the fields the picker describes the result, for example "Runs every day at 02:00 UTC", and then lists the next three runs after Next:. Use the preview to check your schedule before you save.
Generic connections (Intune, Jamf Pro, REST) can run at most every 15 minutes. Only a shared mailbox can be checked every 1, 2 or 5 minutes, because a check that finds no new mail costs no run fee. See How often a mailbox is checked.
All times are UTC
The Hub has no time zone setting for schedules. Every time you type into Time (UTC) or Cron (UTC) is UTC, all year round. Danish time is UTC+1 in winter (CET) and UTC+2 in summer (CEST), and the schedule does not follow the clock change.
A worked example. Your Company wants the nightly Intune import to finish before people arrive at 07.00 Danish time:
- Choose Daily and type 05:00 in Time (UTC).
- In winter (CET, UTC+1) that runs at 06.00 Danish time.
- In summer (CEST, UTC+2) the same schedule runs at 07.00 Danish time.
- If the run must start at 06.00 all year, change the time to 04:00 UTC when Denmark moves to summer time (last Sunday in March) and back to 05:00 UTC when it moves to winter time (last Sunday in October).
The default daily 02:00 UTC is 03.00 Danish time in winter and 04.00 in summer. The default weekly Monday 09:00 UTC is 10.00 or 11.00.
The schedule fields are UTC, but the dates in the Next: preview and on the connection's page are shown in your own local time. If the preview says 06:00 and you typed 05:00, that is the conversion, not a mistake.
Run a connection now
Run now starts a run straight away, whatever the trigger. It is on each row of the Connections list and in the header of the connection's own page.
- Click Run now. The toast Run queued confirms that the run is waiting to start.
- On the list, the row shows Running… and then the result: the run status with the number created, or the error.
- On the connection's page, the figures and the run history refresh by themselves for a few seconds.
- The run counts toward your monthly credits like any other run. See Usage and credits.
- When the workspace has used its monthly credit allowance, Run now is refused and scheduled runs stop until next month.
- There is no Run now for the Webmercs vendor connection or for the platform rows that Juvaro runs.
- Members do not see Run now. See What members see in the Hub.
Messages you may see
| Message | What to do |
|---|---|
| "Scheduled syncs run at most every 15 minutes. Use Run now for on-demand." | Your cron fires more often than every 15 minutes. Pick a slower frequency. For a mailbox the floor is every minute. |
| "cron expression is empty" | Type a cron in Cron (UTC), or pick a frequency from the list. |
| "no future occurrences" | The cron never fires again. Check the day and month fields. |
| "429 - Monthly credit allowance exhausted - resumes next month or raise the allowance" | The monthly credits are used up. Runs start again on the 1st. |
| "403 - Only a workspace administrator can change connections. Ask an administrator of this workspace." | You are not a Workspace Administrator. Ask one to run it for you. |
All messages are listed in Error and validation messages.