Issues with MediaFlows Event Triggers

What to do

• Check whether you use Cloudinary Flow Engine. 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 15h 5m it lasted.

  Anything that failed between 2026-03-11 18:19 UTC and 2026-03-12 09:23 UTC may need a replay.

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

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

Updates from Cloudinary 3

1. investigatingMar 11, 2026, 6:19 PM UTC

   We want to inform you that we have identified an issue affecting MediaFlows where some event-based triggers may not execute as expected. As a result, certain MediaFlows may not run when triggered by events such as metadata updates. Our engineering team is working to restore normal operation, and we will provide further updates shortly.

   provider

2. monitoringMar 11, 2026, 8:36 PM UTC

   We have resolved the issues and are monitoring.

   provider

3. resolvedMar 12, 2026, 9:23 AM UTC

   The recent issue impacting MediaFlows, where some event-based triggers did not execute as expected, has been resolved. All services are now operating normally.

   provider

Corrections

None so far.

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