Internal Courier Error Issue

What to do

• Check whether you use Courier API. Check your stack

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

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

  Anything that failed between 2025-02-28 16:48 UTC and 2025-03-01 04:11 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 7

1. identifiedFeb 28, 2025, 4:48 PM UTC

   The Courier team has identified an issue where messages fail due to an "Internal Courier Error" in the test environment. Our team found the root cause and are working to mitigate the issue.

   provider

2. identifiedFeb 28, 2025, 5:14 PM UTC

   We have tested the fix for "Internal Courier Error" and will be releasing it to production soon.

   provider

3. identifiedFeb 28, 2025, 5:36 PM UTC

   A fix has been merged and will fully deploy within the next hour. Updates to follow.

   provider

4. monitoringFeb 28, 2025, 6:40 PM UTC

   The fix has landed in production and we will be monitoring for any more "Internal Courier Errors". We will be working on reprocessing any dropped messages caused by this issue.

   provider

5. monitoringFeb 28, 2025, 6:57 PM UTC

   Messages with tags are no longer impacted, and error has been resolved. The team is working on reprocessing dropped messages.

   provider

6. monitoringFeb 28, 2025, 7:52 PM UTC

   The team is still working on reprocessing dropped messages caused by this issue. Send pipeline is operational.

   provider

7. resolvedMar 1, 2025, 4:11 AM UTC

   All impacted messages have been reprocessed.

   provider

Corrections

None so far.

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