ReverseProxi

Technical Guide: Webhook Troubleshooting

Webhooks are a powerful way to trigger workflows in real-time, but network issues, server downtime, or payload mismatches can occasionally cause deliveries to fail. This technical guide outlines a systematic diagnostic checklist and explains how to resolve common webhook delivery errors.

Diagnostic Checklist

When a webhook fails to trigger your workflow, work through these diagnostic steps in order:

1. Verify the Endpoint URL: Ensure the external system is sending data to the exact URL displayed in your ReverseProxi trigger settings.

2. Check the Execution Logs: Navigate to the History tab of your workflow to see if the trigger registered the incoming request.

3. Inspect the Payload Format: Ensure the incoming data is valid JSON. Malformed JSON payloads will be rejected automatically by our gateway.

4. Test Manually with cURL: Use a command-line tool to send a mock payload directly to your endpoint to isolate whether the issue lies with the sender or the receiver.

Testing Your Endpoint with cURL

You can test your webhook trigger endpoint by running the following cURL command in your terminal. Replace the placeholder URL with your actual ReverseProxi webhook URL:

curl -X POST https://hooks.reverseproxi.com/v2/trigger/wf_123456 \
  -H "Content-Type: application/json" \
  -d '{"test": "true", "event": "manual_test"}'

Common Error Codes & Explanations

If our gateway rejects an incoming webhook, it will return an HTTP status code. Here are the most common codes and their meanings:

• 400 Bad Request: The payload is not valid JSON, or is missing required headers.

• 401 Unauthorized: The webhook signature verification failed. Check that your signing secret is configured correctly.

• 429 Too Many Requests: Your workspace has exceeded its concurrent rate limit. Contact support to increase your rate limits.

• 503 Service Unavailable: Our servers are temporarily undergoing maintenance. The sending system should retry the delivery.

Retry Logic & Resiliency

ReverseProxi automatically retries failed outgoing webhooks up to 5 times using an exponential backoff strategy (waiting 5s, 15s, 1m, 5m, and 15m between retries). For incoming webhooks, we recommend configuring the sending system to implement a similar retry policy to ensure maximum data resiliency during temporary network disruptions.