- Run fails
- Deployment fails
- Deployment succeeds
- A new error group appears, regresses, or is unignored
If you want to be told about every run that fails, choose a run fails alert. An Error group
alert will not do this — it deliberately stays quiet once it has alerted on a given error.
How to setup alerts
1
Create a new alert
Click on “Alerts” in the left hand side menu, then click on “New alert” to open the new alert modal.

2
Choose your alert method
Choose to be notified by email, Slack notification or webhook whenever:
- a run fails
- a deployment fails
-
a deployment succeeds

3
Delete or disable alerts
Click on the triple dot menu on the right side of the table row and select “Disable” or “Delete”.

Limits alerts
A Limits alert watches limits that can interrupt or degrade runtime flow. Pick one limit for a single alert, or several (or “Watch all limits”) for one combined alert.Signals
Each limit has up to two signals. Choose one or both:- Limit reached: the limit is already affecting traffic, for example requests are being rejected.
- Approaching the limit: usage has reached a share of the limit. The default is 80%, and you can change it.
Any or all
When you watch more than one limit, choose when the alert raises:- Any: raise when at least one selected limit is true.
- All: raise only when every selected limit is true at the same time.
Queue metrics
Environment concurrency and queue size need queue metrics for your environment. If they aren’t available, they aren’t offered when you create the alert.No data
A limit shows “No data” until its metrics exist, for example before your environment has made any API requests or received any webhooks. You can query these metrics yourself, see Platform limit metrics. You can also create these alerts with the API.Error group alerts
Error group alerts are issue-based, not run-based. They are created from the Errors page in the dashboard (the “Configure alerts…” button), not from the New alert modal on the Alerts page. Once created they show up in the Alerts table alongside your other alerts, labelled “Error group”. An error group is one distinct error — the same error from many runs is a single group, with a status of Unresolved, Resolved or Ignored that you set from the Errors page.When an error group alert fires
The alert only fires when a group’s status changes in one of these three ways:Why it goes quiet
This is the part that surprises people, so it is worth stating plainly: An Unresolved error group does not alert. After an error group alert fires, the group is set to Unresolved, and it stays silent no matter how many more times that error occurs. It will only alert again once you mark it Resolved (and it then recurs) or Ignored (and the ignore condition is breached). This is intentional — one persistently broken task should not flood your Slack channel with a message per failed run. But it means an Error group alert is not a substitute for a run failure alert. If a task has been failing in production for days and you have had no notification, check whether the only alert you have configured is an Error group alert whose group is sitting at Unresolved.Which alert type should I use?
- “Tell me about every run that fails” → a run fails alert, from the Alerts page. It fires for every run that fails once its retries are exhausted.
- “Tell me when something new breaks” → an Error group alert, from the Errors page.
Alert webhooks
For the alert webhooks you can use the SDK to parse them. Here is an example of how to parse the webhook payload in Remix:Common properties
When you create a webhook alert, you’ll receive different payloads depending on the type of alert. All webhooks share some common properties:The type of alert webhook. One of:
alert.run.failed, alert.deployment.success, alert.deployment.failed, or alert.errorRun Failed Alert
This webhook is sent when a run fails. The payload is available on theobject property:
Deployment Success Alert
This webhook is sent when a deployment succeeds. The payload is available on theobject property:
Git metadata for the deployment (optional). When present,
branch, commitSha, commitMessage, commitUrl and branchUrl are always set.Deployment Failed Alert
This webhook is sent when a deployment fails. The payload is available on theobject property:
Git metadata for the deployment (optional). When present,
branch, commitSha, commitMessage, commitUrl and branchUrl are always set.Error Group Alert
This webhook is sent for an error group alert. The payload is available on theobject property:

