Delivery Callback Logs
Monitor automated delivery webhooks dispatched to your infrastructure. Debug HTTP return codes, payload response benchmarks, and manage automated retry triggers.
Delivery Callback logs help you track each and every delivery report we sent it back to your Allowlist URL.
On the page that opens, you will see the following:
- Delivery Callback Logs
- Filters
- Test and Live version tabs.
Delivery Callback Logs
The logs that are seen on the "Delivery Callback Logs" page give you an overview of all the Delivery Callback sent to the Allowlist URL. Each log will have the below details.
- Timestamp: Tells you the details of when (date and time) the delivery report was sent to the Allowlisted URL.
- Notification Event: Notification Event for which the callback request was triggered.
- Allowlist URL: Allowlist URL where the delivery report was sent. You can find the list of Allowlist URLs under Workspace Settings -> Allowlist URL.
- HTTP Status Code: HTTP status code of the callback request. The status code can be anything, be it success (200, 201, 2xx etc.) or failure (4xx or 5xx).
- Response Time: Time it took to send the delivery report to the Allowlist URL.
Filters
You can filter the logs based on the criteria mentioned below.
- Timestamp: Tells you the details of when (date and time) the notification event was triggered. You can select one of the provided options, which are:
- Today
- Yesterday
- Last 7 days
- Custom - select a timestamp based on the log retention settings for delivery callback logs. You can see this under Workspace Settings -> Add On's -> Logs Archival
- Message Id: A unique id generated for the notification event that was triggered.
- Custom Id: Shows the Custom Id configured as part of the callback.
- Allowlist URL: Allowlisted URL where the delivery report was sent.
- HTTP Status Code: HTTP status code of the callback request. The status code can be anything, be it success (200, 201, 2xx etc.) or failure (4xx or 5xx).
On clicking the individual Callback log, you will see the Request and Response payloads with each request.
Test & Live Versions
In the logs section, the Test and Live versions are uniquely partitioned, to show you the details notifications sent in that particular version of the API that has been generated.
Can't find a notification log?
Check the environment that the notification was triggered in. Notification triggered in Test environment cannot be seen in Live and vice versa.How to retry failed callbacks
By default, Fyno will attempt 3 times to send delivery callback.
If the callback continues to fail after these attempts (due to downtime on your end or other issues), you can manually retry them using the 'Retry Failed Callback' button.
When you click this button, a popup will display the number of failed delivery callbacks based on your selected filters. Simply click the 'Retry' button to resend all failed callbacks.