A connection's page: figures, Pause and Resume
Read a connection's figures and run history, pause and resume it, and tell Disabled from Paused.
Who can do thisWorkspace Administrator
Every connection has its own page with its figures, its settings in short form and its run history. Click a connection's name on the Connections page to open it. Everyone can read the page; only a Workspace Administrator sees the buttons.
The Integration Hub is in English only, so its labels are quoted in English in the Danish articles too.
The header
The header starts with the breadcrumb ConnectionsSupport inbox, where the last part is the connection's name. Click Connections to go back to the list.
Under the name a row of chips tells you what the connection is:
- The direction: Inbound, Two-way or Outbound.
- The status: Enabled, Disabled or Paused. An auto-paused connection also shows the reason in red, for example "Auto-paused after 3 consecutive failed runs - last error: …".
- The source host, for example the mailbox server or the API address.
- The provider or connector, for example Microsoft 365 or Microsoft Intune.
- Where the data lands, as module · entity.
On the right are the actions: Run now, Pause or Resume, and Edit. Edit opens the same editor as the Connections list and brings you back here when you save or cancel.
- The page has no tabs. Everything is on one scrolling page.
- There is no Delete here. You delete a connection from its row on the Connections list. See Deleting a connection.
The figures
| Figure | What it shows |
|---|---|
| Last run | How long ago the last run started, with its status and the number of records. |
| Next run | When the schedule runs next, as a relative time and a date in your local time. A dash means no scheduled run, for example a manual or disabled connection. |
| Success 30d | The share of runs in the last 30 days that succeeded, with "N retries · N dead-lettered" below. |
| Records 30d | Records processed in the last 30 days. |
| Credits this month | Credits this connection has used this month, with the rate "1 credit/run (+5/MB)". |
If the figures cannot be loaded, the page says "Stats unavailable right now - the run figures could not be loaded." The dashes then mean "unknown", not "no runs yet".
The cards
- Trigger & schedule: the trigger, the schedule in words (always UTC), the next run, and On failure. For a connector it reads "Up to 10 delivery attempts with backoff; auto-pauses after 3 consecutive scheduled failures", followed by the current streak, for example "(2 of 3)". For a shared mailbox it ends "never auto-paused".
- Mapping summary: for a mailbox the fixed mapping "Message subject → Ticket subject", "Sender → Ticket requester" and "Message body → Ticket description". For Intune and Jamf Pro the map is fixed by the connector. For REST you see your own field mappings and an Edit mapping link.
- Credential: how the connection signs in, when the credential expires and its status, with Rotate and All credentials. See Credentials: expiry dates and rotation.
- Alerts: the connection's alert rules. See Alert rules and Needs attention.
- Webhook trigger: Intune, Jamf Pro and REST connections only. See Webhook triggers.
- Run history: every run with Status, Trigger, Started, Finished, Duration, Records and Error. Load more fetches older runs, and a long error opens in full when you click it.
Pause a connection
Pausing stops the runs without touching anything else. Use it while a source system is being changed, or while you investigate errors.
1/5On the connection’s page, click Pause. Pause and Resume are only on this page, not in the list.
- On the connection’s page, click Pause. Pause and Resume are only on this page, not in the list.
- Confirm with Pause. Nothing is deleted.
- The status chip now says Disabled and Next run is empty.
- To start it again, click Resume. There is no confirmation.
- Enabled again. Resume also clears any failure streak, so an auto-paused connection gets a fresh start.
- Click Pause in the header.
- The dialog Pause this connection? explains: "Runs stop until you resume this connection. Nothing is deleted - the configuration, mapping and credential all stay intact."
- Click Pause. The toast says "Paused - runs stop until resumed", and the status chip changes to Disabled.
Pausing is the same as switching Enabled off in the editor. You can still click Run now on a paused connection.
Resume a connection
Click Resume. There is no confirmation. The toast says "Resumed - the pause and the failure streak are cleared". The status goes back to Enabled, the failure count in On failure starts from zero again, and the schedule picks up from the next run time.
Disabled or Paused?
| Status | How it happened | What to do |
|---|---|---|
| Disabled | Someone paused it, or saved it with Enabled off. | Resume when you are ready. |
| Paused | The Hub paused it after 3 consecutive scheduled runs failed. The red reason shows the last error. | Fix the cause (often an expired credential), then Resume. |
- Only scheduled failures count toward the streak, and a successful run resets it.
- A shared mailbox is never auto-paused, so it is never Paused. It keeps trying on its schedule.
- Pause and Resume exist only on this page, not on the Connections list.
Add the alert rule When this connection pauses so the Connections page tells you as soon as a connection is auto-paused.
The Webmercs page is different
The Webmercs vendor connection never runs on a schedule, so its page has no figures, no Pause and no run history. It shows the card Vendor connection (Shop, API user, Password, Order user) with Test connection, the Credential card, and the actions Edit and Delete. See Connecting your vendor's Webmercs shop.
If you follow an old link, the page may say Connection not found: "It may have been deleted, or the link may belong to a different workspace." Use Back to Connections.