On Monday 8 June 2026 between 08:30 and 18:00 CEST, time-based triggers were not executed. These triggers are used for background processes such as clean-up actions and, in some cases, synchronizations with external systems.
A shorter interruption occurred on Tuesday 9 June 2026 between 09:50 and 10:20 CEST after a second rollback.
During these windows, scheduled background processes were delayed. This may have affected clean-up actions and some synchronizations with external systems.
The issue was caused by an incompatibility introduced during the automated rollback after the 1.66 release.
The rollback moved the platform back to an older version, but some time-based trigger state had already been created by the newer version. After the rollback to 1.65, the platform was unable to process part of that persisted state correctly. As a result, time-based triggers stopped executing.
We have added alerting to detect when time-based trigger execution drops significantly. We will also improve rollback testing, so incompatibilities between versions can be detected before they affect production.