Webhooks are being delayed

We are currently experiencing issues with delayed webhooks. Our team is actively working on the fix. We will share new updates within the next hour.

Our engineers have released the fix that partially mitigates the issue. Now we are working on the final development to resolve the issue of delayed webhooks. We still observe the delay in webhook delivery.

Our engineers continue working on the additional development work to resolve this issue. We will provide the next update within the next 60 minutes.

Our engineering team has deployed an additional fix, and the system is now processing the delayed webhooks. The team is monitoring the system and its progress towards processing the queue. We will provide the next update within the next 60 minutes.

Our engineering team's monitoring shows that the underlying issue has been mitigated. We are working through processing the backlog of delayed webhooks and expect delivery to catch up later today. We will post another update once the backlog has fully cleared.

As we continue to recover from the earlier incident, some webhooks may be delivered out of order. Newly generated events can arrive before delayed webhooks that are still in our backlog. We estimate the remaining backlog will be fully cleared within approximately 5 hours.

In the meantime, we recommend performing a GET request upon receiving any webhook, as our system will always reflect the most current data for the associated card.

We will continue to share updates as we make progress, with our next update scheduled for 21:00 UTC.

The backlog of events continues to clear; however, current estimates are that the queue will take approximately 4 hours to clear. We will share our next progress update around 23:30 UTC

Our event backlog is continuing to clear, we estimate the remaining queue should be fully caught up in about 3 hours. Thanks for your patience, we'll share our next update around 2:30 UTC, or sooner if the backlog clears early.

Progress on clearing the event backlog is taking slightly longer than expected. We currently estimate another 3 hours to fully process the remaining queue. We will share our next progress update around 5:30 UTC, or as soon as the backlog clears.

The event backlog continues to clear. Based on current progress, we estimate the remaining queue should be fully processed in approximately 3 hours. We will share our next progress update around 7:30 UTC, or as soon as the backlog clears.