Welcome to our status page. If you are looking for help, please check our documentation guides or contact us on our community forum. All products listed below have a target availability of 99.9%.
Between May 21, 2026, 09:00 UTC and May 25, 2026, 09:00 UTC, a very small subset of customers in the Europe region saw intermittent failures across several Automation Cloud features:
User licenses not deallocating after assignment changes
All other regions were unaffected.
On May 21 at 09:00 UTC, a planned infrastructure migration transitioned an internal messaging service to a new deployment environment. During the migration, a required runtime configuration governing downstream subscription handlers was not carried over correctly. As a result, certain handlers were treated as inactive, causing related events to be dropped.
These subscription handlers support several internal services. Depending on the affected service functionality, some operations experienced delays, timeouts, or completed in an inconsistent state.
The first signals came from support tickets about Solution install/uninstall timeouts and from internal users hitting Studio Web debug failures. Automated alerts for elevated Solutions errors did fire, but at a non-critical severity, and the symptoms looked feature-specific rather than like a messaging-events layer issue. Because the failures were distributed across several seemingly unrelated features, correlating them back to the messaging migration took longer than it should have. The customer-facing status page entry was published retrospectively, after the cause was understood and corrected.
On May 25 at 09:00 UTC, we applied the missing configuration to the new deployment and event delivery to subscribed internal services resumed. After that, we replayed whatever events could be safely re-emitted, so downstream services could reconcile.