Delay in Message Processing

What to do

• Check whether you use Courier Web Application, API, Observability. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 3m it lasted.

  Anything that failed between 2024-08-19 18:32 UTC and 2024-08-19 21:35 UTC may need a replay.

• Subscribe to Courier's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=courier works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Courier 6

1. identifiedAug 19, 2024, 6:32 PM UTC

   The Courier team identified an issue in our health monitoring involving our message event processing. The issue has been identified and a revert is in place.

   provider

2. monitoringAug 19, 2024, 6:48 PM UTC

   Our team has released a revert to address the regression and it's in the process of merging.

   provider

3. monitoringAug 19, 2024, 6:50 PM UTC

   The release is live, and the team is monitoring it.

   provider

4. monitoringAug 19, 2024, 6:56 PM UTC

   Release is published and building to production. ETA ~45 minutes.

   provider

5. monitoringAug 19, 2024, 8:02 PM UTC

   Fix has been deployed, and enqueued messages have started to go through slowly. Once the bottleneck clears, messages should start to flow normally.

   provider

6. resolvedAug 19, 2024, 9:35 PM UTC

   The general pipeline has recovered.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.