We've indentified one possible root cause which could result in processed messages being rescheduled for processing again by the automation system.
Update · UTC
The backlog of background jobs has been processed and things should be snappy again. We're continuing to investigate the root cause of this issue.
Identified · UTC
We've identified a situation where a number is constantly rescheduling new jobs in the background job queue causing it to grow constantly.
Update · UTC
Due to a problematic release, there are quite a few messages pending to be processed and still due for delivery. We are working through the backlog and services relying on the automation system should be responsive again shortly.