Notifications
Where notifications are set up
- Global recipients — Setup → Runtime → Failure notification recipients receive an email whenever any job or schedule ends in failure, plus the warning and long-running emails and the secret-expiry warnings. The field is enabled once an email transport is configured.
- Per job and per schedule — the Notifications section of the job and schedule forms adds Failure email recipients for that object, and on Enterprise Webhook subscriptions.
- Transport — Setup → Runtime → Email for notifications, see Email for notifications.
The emails Cloud Connector sends
| When | To | |
|---|---|---|
| Job or schedule failed | a run ends failed, aborted by restart or timed out; a schedule whose jobs all ran but some failed says completed with failures | global recipients and the object's own |
| Job completed with failures or warnings | a job carried on past failed steps, or its datasets ended with warnings; the mail lists the steps and datasets | global recipients and the job's |
| Job still running | a job has run longer than Long-running job warning (default 120 minutes); sent once per run, nothing is stopped | global recipients and the job's |
| Client secret expiring | the Cloud Connector or Cloud Connector Service secret expires in 30, 14 or 7 days, or has expired | global recipients |
| Sign-in expiring | a Microsoft sign-in refresh token on an action or instance expires within a week, or has expired | global recipients |
| Test email | Send test email in Settings | the address you give |
Subjects start with the From name in brackets and, once the install has several environments, end with the environment's name. Someone who already received a job's failure mail is not sent the schedule's roll-up of the same run. A link to the run is included when the deployment knows its UI URL.
Outbound webhook subscriptions
On Enterprise, a job or schedule can POST its lifecycle events to your URL. In the Notifications section, Add webhook asks for a Name, the URL (HTTPS; private addresses are refused) and the Events: Start, End — Success, End — Failure and Still running (fires once when the run passes the long-running threshold). Each subscription has a secret, shown once and rotatable with Rotate secret; a Send test event and a View delivery history (the last 50 deliveries with status, HTTP code, attempt and duration).
Each delivery is a JSON body with the event name, a delivery id, the time,
the subscription, and the run document, with the headers
X-Cloud-Connector-Event, X-Cloud-Connector-Timestamp and
X-Cloud-Connector-Signature: t=<timestamp>,sha256=<hex>. Verify it by
computing HMAC-SHA256 over <timestamp>.<body> with the secret. A delivery
that fails is retried after 30 seconds, 2, 10 and 60 minutes; after ten
consecutive final failures the subscription is disabled, and re-enabling it
resets the count.