Issues with MediaFlows Event Triggers
Mar 11, 18:19 UTCMar 12, 09:23 UTC
Duration
15h 5m
Impact
Minor
Root cause
Not disclosed
Cloudinary, 90 days
5 incidents
Affected
Flow EngineMediaFlows - Flow Engine
Final update
The recent issue impacting MediaFlows, where some event-based triggers did not execute as expected, has been resolved. All services are now operating normally.
Timeline
- Resolved · Mar 12, 09:23 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.
- Monitoring · Mar 11, 20:36 UTC
We have resolved the issues and are monitoring.
- Investigating · Mar 11, 18:19 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.
More from Cloudinary
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Aug 1317:04 UTC | Media Library / asset visibility | minor | 24h 41m |
| Jul 2913:35 UTC | Add-on installations are unavailable | minor | 1h 22m |
| Jul 2023:09 UTC | Connection failures with the Cloudinary MCP Connector | minor | 12h 16m |
| Jul 1410:17 UTC | Some customers experience authentication problems when accessing Cloudinary's Figma plugin | minor | 0m |
| Jul 1210:20 UTC | Elevated Error Rates for Requests Using g_auto | major | 2h 24m |
| Jun 1615:19 UTC | Delays in MediaFlows | minor | 15h 17m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.