Marketing Cloud automations failing to reschedule following network or database performance incidents
Trailblazer Community

Marketing Cloud automations failing to reschedule following network or database performance incidents

Marketing Cloud Automations

Last updated 12 days ago ·Reference W-5659603 ·Reported By 9 users

In Review

Summary
When incidents such as network latency or database contention occur while attempting to schedule the next occurrence of an automation, the currently scheduled automation doesn't run and the next scheduled instance is not created. This results in the scheduled automation not running future occurrences until a user manually reschedules it. This has been acknowledged as a defect and correction is planned for a future Marketing Cloud release.

Repro
Previously running automation affected by database/performance incident

Workaround
Manually reschedule the automation

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.