Automation left in Queued Status
Last updated 2021-11-01 ·Reference W-7349161 ·Reported By 2 users
Occasionally, when a Triggered Automation runs, a state may be encountered where an automation instance is left in a queued status.
This is not going to be easily reproducible as it is an intermittent problem.
Re-running the automation/re-dropping the file that was used when the instance was left in a queued status.
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.