Issue Summary: Between 2nd April 2025, 19:25 UTC and 3rd April 2025, 03:50 UTC, scheduler trigger-oriented journeys experienced delayed executions. This affected only interval-based scheduler journeys; cron expression-based journeys continued to run as expected.
Journeys scheduled within the mentioned time window may have faced delayed execution or shifted trigger intervals.
We recommend users to: - Review any scheduler-triggered journeys configured with interval-based scheduling that fall within the affected window (2nd April 19:25 UTC to 3rd April 03:50 UTC). - If your journey execution time appears shifted or missed, please restart or reconfigure the interval to the correct intended value.
We apologize for the inconvenience and appreciate your understanding.