What Does “Export Failed” Mean?
When Parseur sends a webhook, it delivers data from Parseur’s system to another external server or service. A failed webhook occurs when the intended server does not successfully receive or process the data sent by Parseur.
Common Causes of Failed Webhooks:
Server Issues: The receiving server is down, busy, or experiencing an outage.
Slow Response Time: Parseur waits up to 30 seconds for a response. If the server takes longer, the webhook is marked as failed.
Unexpected Data: The data sent by Parseur doesn’t match what the receiving server expects (e.g., incorrect format or missing fields).
Authentication Errors: The receiving server denies the request due to authentication issues.
If you’d like to get more information about the issue, navigating to your document logs can help you find out why the webhook failed.
Getting More Information on a Failed Export:
Failed webhook events can be a daunting issue to debug. It's important to check the logs, error message, and other details to properly diagnose the issue. Here are two simple steps to help you get more information about a failed webhook event:
1. View Logs:
The Log button is represented by a 🔎 magnifying glass icon on a document.
You can access the button from either:
The document list page by hovering over a document.
The document view page (top-right corner).
2. Check the Error Message:
The log entry will display the HTTP status code and any error message from the receiving server.
Click “show details” for more in-depth information about the failure.
Automatic Retry Mechanism for Failed Webhooks
Parseur will automatically retry failed webhooks up to five times, for a total of six attempts.
Triggers for Retry:
HTTP 408 (server timeout)
HTTP 429 (too many requests)
HTTP 500-599 (server errors)
Connection Timeout (unable to connect to the server)
When No Retry Will Occur:
Any HTTP code other than the ones mentioned above
In case of a read timeout (connection succeeded, but no response received).
Exponential Back-off Timing:
1 minute after the first failure.
Subsequent attempts are made at 4, 9, 16, and 25 minutes intervals to avoid overloading the receiving server.
This retry policy applies to custom webhooks and integrations with Zapier, Make, Power Automate, etc. All actions, including retries, are visible in the document logs.
Troubleshooting Failed Webhooks:
Check Server Configuration
If the data is being sent to your server, involve your developers or system administrators to inspect the logs and configurations.
Third-Party Services:
If the webhook connects to platforms like Zapier, Make, or Power Automate, consult their documentation or contact their support team.
Frequently Asked Questions (FAQ)
Can the 30-second timeout limit be increased?
Yes, this limit can be adjusted on a case-by-case basis. Contact Parseur support via chat to discuss.