Open the logs
Open the portal’s notification settings and find Integrations & Webhooks, then select View Logs. Slack and Discord integrations require Pro or Enterprise. Custom webhook features require Enterprise.
The logs show the destination, event type and delivery result. Use Filter logs to narrow the list by event type or by Success and Failed. Expand a log to inspect the available details, including the saved payload where present.
Retry a failed delivery
- Find the failed log and expand it to check the destination and details.
- Correct any problem with the receiving service or webhook configuration.
- Select Retry webhook on the log.
- Wait for the result and check the latest log details.
A retry is available only when the original delivery failed, a payload was saved and the log has not already been delivered successfully on retry. A retry sends that saved event again; it does not create new feedback.
Older logs may show This older log has no saved payload. Those deliveries cannot be retried from the log because there is no saved event body to send.
Check an uncertain result
A successful retry is marked Delivered on retry. If the app says it could not confirm the retry, check both the latest logs and the receiving service before trying again. The destination may have received the request even if the app did not get a confirmation.
Use the response or error details to decide what to investigate. A missing destination, a rejected request and a temporary service failure need different fixes.
Save notification changes
Changing a webhook URL or the event switches is separate from retrying an old delivery. Save your notification settings, then use a new test event to check the configuration.
Review email and notification preferences for the other notification settings.