Due to a misconfiguration on our side the requests were failing, this allowed us to see that when the connection timeout we end up with orphaned WebhookResponse records in event_activity_responses as they're not attached to any request.
As you can see in the image above the records 26 and 27 have no request_id.
Hi there,
Due to a misconfiguration on our side the requests were failing, this allowed us to see that when the connection timeout we end up with orphaned WebhookResponse records in
event_activity_responses
as they're not attached to any request.As you can see in the image above the records
26
and27
have norequest_id
.