Troubleshooting
Find your problem below. Each one lists the symptom you will see, the usual cause, and the fix.
Webhook not firing
- Symptom: A record changes, but no webhook is sent and no new log entry appears.
- Cause: The webhook's Is Active box is not ticked, or the Event Type does not match the change you made (for example, the webhook is set to Create but you edited an existing record).
- Fix: Open the webhook configuration, tick Is Active, check the Event Type and Target Object, save, and try again. Then check the Logs tab.
401 error
- Symptom: Deliveries fail with status code 401, or inbound requests are rejected with 401.
- Cause: Authentication failed — for outbound webhooks, the Named Credential's authentication is wrong or has expired; for inbound webhooks, the secret header is missing or incorrect.
- Fix: For outbound, check the authentication on the Named Credential (see Setup: Named Credential). For inbound, check the sender is including the correct secret header (see Inbound Webhooks).
404 error
- Symptom: Deliveries fail with status code 404.
- Cause: The endpoint address is wrong — usually the relative path in the Endpoint URL, or the Named Credential's base URL.
- Fix: Check the Endpoint URL is the correct relative path only (for example
/webhooks/v1/lead-listener), and check the base URL on the Named Credential. For inbound, check the URL matches/services/apexrest/bytenex/v1/webhookexactly.
Named Credential error
- Symptom: The webhook fails and the log points to the Named Credential.
- Cause: The Named Credential named in the webhook configuration does not exist, its Developer Name does not match, or its authentication is not set up.
- Fix: Go to Setup → Named Credentials, confirm the credential exists, and copy its exact Developer Name into the webhook configuration. See Setup: Named Credential.
Log shows Failed
- Symptom: A log entry in the Logs tab shows status Failed.
- Cause: The endpoint rejected the delivery or could not be reached — the status code and response body in the log show what the endpoint said.
- Fix: Open the log entry, read the status code and response body, fix the cause (the entries above cover the common codes), then click Retry on the log entry. See Logs & Retries.
Flow not triggering
- Symptom: A Flow containing the Send Webhook action does not run, or runs but sends nothing.
- Cause: The Flow is not active, its trigger conditions do not match the record change, or the action is not passing the record ID.
- Fix: Activate the Flow, check its trigger conditions, and confirm the Send Webhook action passes
$Record.Id. See Use with Flows.
Still stuck? Contact Support.
Was this helpful? Let us know by email — we read every message.