Skip to main content

Troubleshoot webhooks

Use the Communications log to investigate failed webhook notifications and identify the root cause.

Inspect failures in the Communications log​

  1. In the Mambu UI, open the Communications tab.
  2. For a more detailed view:
    • Select Edit Columns.
    • Enable Include timestamps.
    • Add Creation Timestamp, Failure Reason, and Failure Details.
  3. Locate the failed webhook notification, open the details, and review payload and response status.
  4. Apply filters (for example, status = Failed, time range) to narrow results. Prefer small time ranges to avoid heavy queries.

Common failure reasons​

  • Destination unreachable (404 Not Found): The webhook URL is incorrect or the endpoint is down.
  • Unauthorized (401 Unauthorized): The API key or authentication method is incorrect.
  • Timeout: The destination server took too long to respond.
  • Payload too large or malformed: The receiver rejected the message.
  • Blacklisted URL: Sending to restricted addresses is blocked.

Resend options​

  • Manual resend from the Communications log for individual items.
  • Programmatic resend via API. See Managing notifications.

Improve reliability​