Articles on: Integrations

Webhook Logs: Monitor and Troubleshoot Your Webhooks

Webhook Logs: Monitor and Troubleshoot Your Webhooks


In this article:

  • Overview
  • How to open the Webhook Logs
  • What each column shows
  • How to filter and search the log
  • How to see the full details of a delivery
  • How failed deliveries are retried
  • The Health column on your webhooks
  • Things to keep in mind
  • FAQs
  • Who can do this


Overview


The Webhook Logs page shows every attempt SuperPath has made to send a webhook from your account in the last 30 days. For each attempt you can see which event was sent, to which webhook, whether your endpoint accepted it, what it answered, and how long it took. You can also open any attempt to see the exact payload that was sent and the response that came back.


Use it when a system connected by webhook seems to be missing data, when you are building or testing a new endpoint, or when the Health column on a webhook says it is failing.


Note: Webhooks are only available on paid accounts. On a free plan the Webhook Logs page shows a message that webhooks are only available for paid accounts, with a link to your Billing settings.


How to open the Webhook Logs


  1. Go to Settings → Integrations and scroll to the Manage Webhooks section.
  2. Click View Webhook Logs, next to Add Webhook. The log opens for every webhook in your account.


To open the log for one webhook only, click the View logs (list) icon in that webhook's row instead. The log opens with that webhook already chosen in the filter.


To get back to your webhooks, click the back arrow next to the Webhook Logs heading.


What each column shows


Each row is one delivery attempt, newest first, 30 to a page.


Column

What it shows

Date

When the attempt was made.

Event

The event that was sent, for example user.updated.

Webhook

The webhook the attempt was sent to.

Attempt

Which attempt this was, out of a maximum of six, for example 2 of 6.

Outcome

Delivered, Will retry, Failed or Skipped. See below.

Status

The HTTP status code your endpoint answered with, or None if it gave no answer (for example a timeout).

Duration

How long the attempt took, in milliseconds.


The four outcomes mean:


  • Delivered: your endpoint answered with a 2xx status code.
  • Will retry: the attempt failed in a way that is often temporary, so another attempt has been scheduled.
  • Failed: the delivery has stopped. Either the failure is one SuperPath does not retry, or all six attempts have been used.
  • Skipped: SuperPath did not call your endpoint. This happens when the webhook URL points somewhere SuperPath will not send to (for example a private network address), or when a scheduled retry finds the webhook has since been deleted, switched off or no longer subscribes to that event.


How to filter and search the log


  • Filter: use the filter dropdown to narrow the log to one Webhook, one Event or one Outcome. For example, choose Failed to see only the deliveries that did not get through.
  • Date range: pick a start and end date to see attempts made between those dates.
  • Search: enter a record id or a delivery id to find every attempt for it. The search matches the whole id exactly, so paste it in full.


The record id is the id of the user, learning, team or other record the event was about. It is the same value as data.id in the payload your endpoint received.


How to see the full details of a delivery


Click any row to open the delivery's details on the right. They show:


  • the Webhook and the URL the attempt was sent to;
  • the Delivery id, which stays the same across every attempt of one delivery;
  • the Record the event was about;
  • the Outcome, with the time of the next attempt if one is scheduled, and a short explanation when the attempt did not succeed (for example "No response within 10 seconds");
  • every Attempt of this delivery so far, with its time and result, plus the next scheduled attempt;
  • the Request payload exactly as it was sent, shown up to the first 64 KB;
  • the Response your endpoint sent back: its status code and the first 2 KB of the body.


Good to know: The SuperPath-Signature header and your webhook's secret key are never stored in the log, so nobody can read them from this page.


How failed deliveries are retried


When an attempt fails in a way that is often temporary, SuperPath tries that delivery again, up to six attempts in total. The wait before each retry is:


Attempt

Sent

1

When the event happens

2

1 minute after attempt 1

3

5 minutes after attempt 2

4

30 minutes after attempt 3

5

2 hours after attempt 4

6

6 hours after attempt 5


That covers about 8.5 hours from the first attempt.


These are retried: no response within 10 seconds, a connection that could not be made or was dropped, and the status codes 408, 429, 500, 502, 503 and 504.


These are not retried: any other 4xx or 5xx status code, and any redirect (3xx). SuperPath does not follow redirects, so if your endpoint has moved, update the webhook's Endpoint URL.


A retry only goes to the webhook that failed. Other webhooks on the same event that already succeeded are not sent the event again. Before each retry SuperPath checks the webhook again, so if you delete it, switch it off or unsubscribe it from that event in the meantime, the retry is logged as Skipped and the delivery stops. If you correct the webhook's URL, the remaining retries go to the new URL.


For how your endpoint can recognise a retry, see Webhooks - Get updates in real-time.


The Health column on your webhooks


The webhooks table in Settings → Integrations → Manage Webhooks has a Health column, so you can spot a problem without opening the log:


  • Healthy: the webhook's last delivery succeeded, and it has delivered at least once in the last 30 days.
  • N failing: the last N deliveries in a row ended as Failed. Hover over the badge to see when the last failure happened. It goes back to Healthy as soon as a delivery succeeds.
  • No recent: nothing is failing, but there has been no successful delivery in the last 30 days, or ever. This is normal for a new webhook, or for one subscribed to events that rarely happen.


A delivery counts once, on its final result. A delivery that fails once and then succeeds on a retry does not count as failing, and a Skipped attempt does not count either way.


SuperPath does not switch off a failing webhook. It keeps trying every new event until you fix the endpoint or switch the webhook off.


Things to keep in mind


  • Log entries are kept for 30 days and then deleted automatically. There is no export, so copy anything you need to keep longer from the details panel.
  • The log stores the full payload, which can include personal details of your users. Anyone who can open Settings in your account (Owners and Admins) can read it.
  • An attempt usually appears in the log within a minute. The page does not update by itself, so reload it to see new attempts.
  • The Last event date in the webhooks table is the time of the most recent successful delivery. It can be up to five minutes behind the log.
  • SuperPath only sends to public addresses on ports 80 and 443. A URL that points at a private or internal network address is refused when you save the webhook, and logged as Skipped if it later resolves to one.


FAQs


My endpoint was down for an hour. Have I lost those events?
Probably not. Each delivery is retried for about 8.5 hours, so once your endpoint is back up, the next scheduled retries should get through. Check the log for rows marked Failed to find any that ran out of attempts.


Can I resend a delivery myself?
Not from the Webhook Logs page. The log shows the payload in full, so for a delivery that ended as Failed you can copy it from the details panel, or read the current record from the SuperPath API.


Why does the same event show several rows?
Each attempt is its own row. All attempts of one delivery share the same Delivery id, which you can paste into the search box to see them together.


Why was a delivery marked Failed straight away, on attempt 1?
Your endpoint answered with a status code SuperPath does not retry, such as 400, 401, 404 or a redirect. Open the row to see the status code and your endpoint's response, fix the cause, and the next event will be delivered as normal.


What does "Skipped" mean if my webhook is active?
SuperPath refused to call the URL because it points at an address it will not send to, such as a private network address or a port other than 80 or 443. Open the row to see the reason, then update the webhook's Endpoint URL.


Can my partner see my webhook logs?
If your account is managed by a SuperPath partner, the partner can see the same log for your account from their partner portal.


Who can do this


Owners and Admins can view the Webhook Logs, on a paid plan. These are the same roles that can manage webhooks. Managers, Content Managers, People Managers, Instructors, Employees and Restricted users cannot open Settings and cannot read the log.

Updated on: 26/10/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!