Incidents

An Evaluation opens an Incident when a scheduled window fails and no Incident is already open for the associated Expectation.

An Incident groups failures from the same Expectation into one outstanding operational problem, so your team can investigate repeated failures together.

An Incident remains open until the same window later closes as Late, a subsequent window closes as Success, or you resolve it manually.

A later successful window shows that the delivery flow has recovered, but it does not prove that a file missing from an earlier window arrived. Resolving the Incident does not change those earlier Evaluation results; use them to account for each expected delivery.

Managing Incidents

Incidents can be resolved, acknowledged, or snoozed.

• Resolving an Incident closes it and stops any further notifications.
• Acknowledging an Incident signals to colleagues that someone is actively investigating the problem.
• Snoozing an Incident suppresses further notifications in the Web App until a specified time.

Incidents can be viewed and managed from the Expectations detail page in the Web App. Incidents are not generated for manual-triggered windows.

Notifications

To get notified when an incident opens, is acknowledged, snoozed, or resolved, use Event Channels. Subscribe to Expectation Incident events and route them to a webhook, Slack, Teams, SNS, Pub/Sub, or email target.

Site Administrators can also receive email alerts for expectation evaluation failures (Missing and Invalid) through the Expectation failures and misses preference in their account settings. See Alert Emails for Site Administrators.

Details Recorded in Incidents

Incidents contain the following information.