search

datocms / product-roadmap

This project is now discontinued. For feature requests, please use our community forum.
https://community.datocms.com/
19 stars 1 forks source link

Webhook timeout #183

Open james-relyea opened 5 years ago

james-relyea commented 5 years ago

Describe the bug Sometimes when a webhook attempts to fire, we receive a network timeout with response body containing: Net::ReadTimeout. We aren't running any Ruby on our end so I presume it's happening on the Dato side. Clicking Resend on the webhook will result in a successful call.

To Reproduce Steps to reproduce the behavior: Unfortunately it doesn't seem to be easily reproducible as it happens sporadically. None of the webhook calls run longer than a couple seconds so perhaps there's a limit set that we're exceeding?

Expected behavior Would be great if the webhook would attempt a couple retries if it times out for whatever reason on the first attempt, that way we don't have to go into the Activity Log and manually trigger the resend.

matjack1 commented 4 years ago

This feature request has been moved to https://community.datocms.com/t/225