Skip to main content
Braze

Issue impacting Canvases with Exit Criteria

Degraded Lasted 17h 38m · started · Braze's page

Level
confirmed
Worst impact
Degraded
Components
Email, SMS, In-App Messaging, WhatsApp, Push Notifications - iOS, Push Notifications - Android, Content Cards
Regions
us
Down Index
38of 100

What to do

  • Check whether you use Braze Email, SMS, In-App Messaging, WhatsApp and 3 more in us. 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 17h 38m it lasted.

    Anything that failed between 2025-04-15 22:45 UTC and 2025-04-16 16:23 UTC may need a replay.
  • Subscribe to Braze's feed to hear about the next one first. RSS feed

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

Updates from Braze 3

  1. monitoring

    Issue Overview On April 11th, 2025, we released an update that inadvertently introduced a bug affecting Canvas configurations. Unfortunately, this update erroneously added Exit Criteria filters to Canvas Entry Criteria filters for active Canvases with Exit Criteria. This resulted in users who should have qualified for canvas steps being aborted out of impacted canvases and not receiving messages they otherwise qualified for. Current State and Next Steps The issue itself has been mitigated as of 15:28 UTC on Monday, April 14th, so that the unexpected behavior is no longer actively impacting new canvases. With respect to impacted canvases, we are still working to determine the full scope of the impact and the appropriate steps that can be taken to remediate that impact. We understand the impact that this has on you and are working urgently and with executive oversight to resolve all impacts as quickly as possible. Please know that this is a top priority for our engineering organization. We appreciate your partnership and patience while we continue to work through remediation of the remaining impact caused by this issue.

    provider

  2. monitoring

    Earlier this evening, our engineering team completed the impact analysis from this issue, which caused some Canvases that had Exit Criteria to not enter new users. As of approximately 7:30pm ET, we had restored more than 99% of the impacted Canvases to their original and correct state. A small number of customers have received direct outreach from us regarding certain Canvases that were not modified by our team and we will handle next steps directly with them. We will continue monitoring and provide a final update in the morning Eastern time.

    provider

  3. resolved

    Our engineering team has completed all necessary restorations for the Canvases affected by the Exit Criteria issue. As of 7:30pm ET yesterday, we had successfully restored more than 99% of impacted Canvases to their correct state. We are now working directly with the remaining affected customers to address their specific situations and will complete all customer communications by the end of the day. This incident is now resolved. We appreciate your patience throughout this process and apologize for any disruption this may have caused.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-fc72066923

Is Braze still down?

No, this incident was resolved 2025-04-16 16:23 UTC. For Braze's live state, see https://down.guide/braze.

How long did it last?

17h 38m, from 2025-04-15 22:45 UTC to 2025-04-16 16:23 UTC, by the times Braze posted.

What was affected?

Braze named Email, SMS, In-App Messaging, WhatsApp and 3 more in us.

What caused it?

Braze hasn't published a root cause. If it does, it shows here.

Where does this come from?

Braze's official status page, https://braze.statuspage.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.