Alert rules and Needs attention
Add in-app alert rules to a connection, and act on the Needs attention strip.
Who can do thisWorkspace Administrator
An alert rule watches one connection and raises a flag when something goes wrong: the connection is auto-paused, runs keep failing, nothing has succeeded for a while, or the credential is about to expire. Firing alerts show on the connection's page and in a red Needs attention strip at the top of the Connections page.
The Integration Hub is in English only, so its labels are quoted in English in the Danish articles too.
The Alerts card
Alert rules live on the connection's own page, in the card Alerts. A connection without rules shows No alert rules yet and four quick-add chips.
| Quick-add chip | Fires while | Custom range |
|---|---|---|
| + When this connection pauses | The Hub has auto-paused the connection after failed runs. A manual pause does not fire it. | No number |
| + After 3 consecutive failures | The latest runs have failed this many times in a row. | 2 to 10 failures |
| + No successful run in 24 hours | The connection is enabled and has not had a successful run for this many hours. | 1 to 168 hours |
| + Credential expires within 14 days | The expiry date recorded for the connection's credential is this close or has passed. | 1 to 90 days |
Click a chip and the rule is saved at once with the suggested number. A chip is greyed out when exactly that rule already exists ("This rule already exists").
Add a custom rule
- On the connection's page, click Add rule in the Alerts card.
- Open the list Custom rule… and pick a condition.
- Change the number, which starts at the suggestion. The ranges are in the table above.
- Click Add, or Cancel to close without saving.
Each rule then shows on its own line, for example "No successful run in 48 hours", with the channel chip In-app. Rules with a number have Edit, where you change the number and click Save. Delete removes a rule straight away, without a confirmation.
- A connection can have at most 10 rules.
- The same rule cannot be added twice.
- The Webmercs vendor connection has no Alerts card.
Alerts are in-app only
Alerts are shown in the Hub and nowhere else. They do not send email, and they do not appear in the platform's notifications. Someone has to open the Hub to see them, so make checking the Connections page part of your routine.
An alert is not a stored event. It is there while its condition holds and disappears by itself when the condition is fixed: when the connection is resumed, a run succeeds, or the credential gets a new expiry date.
FIRING
When a rule's condition holds, its line in the Alerts card gets a red FIRING badge. The badge goes away when the condition no longer holds.
The Needs attention strip
When at least one alert fires anywhere in the workspace, the Connections page shows a red strip above the figures, headed Needs attention (N), where N is the number of firing alerts. When nothing fires, the strip is not shown at all.
Each line has the connection's name (a link to its page), a short description of the problem, when it began where that is known, and an action:
- Fix credential, for an expiring credential. For a mailbox, Intune, Jamf Pro or Webmercs connection it opens the connection's editor at the secret, ready for a new value. For other connections it opens the Credentials page, where the expiry date is kept.
- View, for every other alert. It opens the connection's page, where the run history and the red pause reason tell the full story.
A good starting set for an important connection is When this connection pauses and Credential expires within 14 days. For a shared mailbox, which is never auto-paused, use After 3 consecutive failures instead of the pause rule.
Members
Members see the rules, the In-app chip and any FIRING badge, but not the chips, Add rule, Edit or Delete. They see the Needs attention strip too. See What members see in the Hub.
If saving fails
A refused save shows "Could not save the alert rules (status): reason" in red on the card, for example when a number is outside its range. The reason names exactly what was wrong. See Error and validation messages.