Prisma1: Retry failed webhook deliveries

Created on 5 Sep 2017 · 2Comments · Source: prisma/prisma1

Currently, if a webhook delivery in a server side subscription fails, the system is not attempting a redelivery.

The upside would be that transient errors (network, hitting a dying server, ...) would be handled gracefully. The downside is that delivering a webhook multiple times is something that might have unintentional side effects if the webhook fails but side effects were already triggered anyways before the remote blew up.

Personally, I'd consider the latter to be bad design on the webhook receiver side and would always assume the implementation to be idempotent or robust enough to handle these cases.

Thoughts?

kinfeature

Source

dpetrick

Most helpful comment

I think webhook should have an options to try failured on http codes: retryHttpCodes: [0, 500, 503, 504]. And another options for connection timeout.

giautm on 21 Apr 2018

👍3

All 2 comments

I think webhook should have an options to try failured on http codes: retryHttpCodes: [0, 500, 503, 504]. And another options for connection timeout.

giautm on 21 Apr 2018

👍3

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.