We have found the cause and impact of this issue. A code change related to improved handling of error logging for actions caused increased database lock contention during the processing of Webhook requests. As a result, requests for a small number of Webhook Actions with expired error log entries timed out (returning a 500 status code) and weren't successfully processed. We are reaching out directly to those customers affected. Thank you for your patience as we resolved this issue.

We are aware of a temporary interruption to Webhook processing requests today August 17th from 15:30 UTC to 16:05 UTC. The issue is currently resolved. We will post an explanation for this issue on this page.