Settings & integrations
Investigate notification deliveries
Filter Secorvia notification attempts by provider, event, and status, then inspect delivery errors and retries.
Reviewed
Before you start
At least one notification must have been attempted. Configure Notifications first if the list is empty.
Choose the provider and event
Open Notification History. Filter Email, Slack, Teams, or Discord and choose the event you are investigating. Use Search error messages if you have a known failure text.
Distinguish delivery states
Filter Pending, Sending, Sent, or Failed. Sent indicates the delivery was sent by the integration; confirm visibility in the destination when investigating recipient-side rules or channel issues.
Inspect the attempt details
Open the delivery’s Details and read Event, Attempts, Created, Next Attempt, and Error. Use the error to decide whether the destination, provider configuration, or external service needs attention.
Verify the corrected configuration
Correct the relevant settings in Notifications and run a test. Return to delivery history to verify the next attempt or new event. Keep the event and destination context in the team’s investigation notes.
Where you are now
You can explain whether a notification was attempted, its current state, and the reason for a delivery failure.
WHEN SOMETHING LOOKS OFF
A few things to check
No notifications sent yet
Send a configured test or wait for a selected event to occur.
No notifications match
Clear provider, event, status, and error-search filters.
PUT IT INTO PRACTICE
Make your next move in Secorvia.
Open the app and follow along with your own organization.