Skip to main content
Webhook Logs lists each webhook event Fluid has tried to deliver for your company. Use it to see whether an endpoint accepted a delivery, and to check the payload and response Fluid recorded.

​
Where to find it

In the admin, click the Settings gear in the top bar. In the Settings sidebar, under System, select Webhooks. On the Webhooks screen, in the banner below the page title, click View Webhook Logs. Webhook Logs has no item of its own in the Settings sidebar or in Settings search.
To open this screen, your role needs view access to Developer. On the Roles screen, set Developer to View only, or turn on its View API keys and webhook endpoints switch. To retrigger events, also turn on Manage webhooks and API configuration.

​
What’s on the screen

The table has four tabs: All, Success, Failed and Pending. It opens on All and lists events newest first. The Success, Failed and Pending tabs currently show no events, so stay on All and use the Status badge to find the events you need. Each row has these columns:
  • Event: the event name, such as order_created. The event’s unique identifier appears in small text below it.
  • Object: the type and ID of the record the event is about, such as Order #1042 or Cart #2210. For orders, the number is Fluid’s record ID, not the order number.
  • Status: a colored badge that shows the delivery result.
  • Response Code: the HTTP status code the endpoint returned. It shows - when no code was recorded.
  • Created At: the date and time Fluid logged the event, in your browser’s time zone.
The Status badge has three values:
  • Success (green): the endpoint returned 200, 201, 202 or 204.
  • Failed (red): any other response code was recorded, including other 2xx codes.
  • Pending (yellow): no response code was recorded.
To narrow the list, type part of an event name, such as order, in the search box above the table.

​
Event details

To open an event, click the three-dot menu on its row, then click View Details. A side panel opens. Its title is Webhook Event: followed by the event name, and it has these sections:
  • Event Details: the event’s Identifier, Status, Response Code and Created At.
  • Payload: the JSON Fluid recorded for the delivery. For its structure, see Register and handle webhooks.
  • Response: what Fluid recorded about the reply, as JSON. This is usually the status code and body the endpoint returned. It can instead show why Fluid got no reply, or why the request wasn’t sent.
Payload and Response appear only when Fluid recorded them. At the bottom of the panel are a Close button and, for events with the Failed status, a Retrigger button.

​
Retrigger a failed event

Retrigger resends the event’s original data to every active webhook subscribed to that event, not only the endpoint that failed. Endpoints that already accepted the event receive it again.
1

Open the failed event

On the All tab, find an event with the red Failed badge. Click the three-dot menu on its row, then click View Details.
2

Click Retrigger

At the bottom of the side panel, click Retrigger.
3

Check for the new entry

Fluid sends the event again, but the side panel stays open and still shows Retrigger. Click Close to return to the table, where each new delivery appears as its own row at the top of the list. The original row keeps its Failed status.Don’t click Retrigger again unless you mean to resend the event to every endpoint. If no new row appears, see Retrigger didn’t add a new row.

​
Troubleshooting

Open the event with View Details. The Response Code and Response show what the endpoint returned. Fix the endpoint, or the webhook’s settings on the Webhooks screen, then retrigger the event.If your endpoint processed the event but returned a code other than those listed for Success, the event still shows as Failed. To avoid this, have your endpoint return 200. For how your endpoint should respond, see Register and handle webhooks.
Pending means Fluid recorded no response code for the delivery. This happens when your endpoint couldn’t be reached or didn’t reply in time, or when Fluid didn’t send the request, for example because the webhook URL isn’t valid, doesn’t use HTTPS, or points to a private host. Open the event with View Details. If a Response section appears, it may give the reason.Fluid doesn’t retry a failed delivery to your webhooks on its own. Retrigger isn’t available for Pending events, so you can’t resend this event from Webhook Logs. To make sure later events arrive, check that your endpoint is reachable and replies promptly. Then check the webhook’s settings on the Webhooks screen.
Retrigger shows no confirmation or error message. If no new row appears after you close the panel, check these:
  • A webhook for this event is still active on the Webhooks screen.
  • The record the event is about, such as the order, still exists.
  • Your role has the Manage webhooks and API configuration switch turned on for Developer on the Roles screen.
Webhook deliveries are queued. They usually go out in near real time, but can lag 5 to 10 minutes when the queue is backed up. An event appears here when Fluid attempts the delivery.Your webhooks send an event only while they’re active and subscribed to it. Check the webhook on the Webhooks screen. Make sure you’re on the All tab. If you searched, clear the search box. Search matches event names only, so an order number or ID finds nothing.