Skip to content

Commit 5e0d42d

Browse files
authored
Update alerting.md - delivery alert functionality
1 parent a8a50bc commit 5e0d42d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

src/connections/alerting.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,4 +56,6 @@ To make changes to a successful delivery rate alert, select the icon in the Acti
5656
To delete a successful delivery rate alert, select the icon in the Actions column for the alert and click **Delete**.
5757

5858
> info "Deleting alerts created by other users requires Workspace Owner permissions"
59-
> All users can delete successful delivery alerts that they created, but only those with Workspace Owner permissions can delete alerts created by other users.
59+
> All users can delete successful delivery alerts that they created, but only those with Workspace Owner permissions can delete alerts created by other users.
60+
61+
Delivery Alerts are generated based on the outcomes of the last two stages in the pipeline: Failed Deliveries and Successful Deliveries. Therefore, Alerts will be determined by the attempts Segment makes to transmit events to your destination, focusing solely on events qualified for dispatch (i.e., those not discarded earlier due to business rules like protocols, destination filters, and mappings).

0 commit comments

Comments
 (0)