Temporary Change to Data Job Execution Settings

This incident has been resolved.

There was no impact during the period and the Data Job Queueing feature that was temporarily disabled has been enabled again. The feature will be active with the next trigger of scheduled executions.

We understand the issue that led to needing to temporarily change the Data Job Execution settings, and have taken steps to reduce any further impact. We look to roll out the final fixes on Monday Aug 4th.

We’ve temporarily disabled the new Data Job Queuing feature that was enabled at the end of April.

As a reminder, our Data Integration system only allows one instance of a data job to run at a time. When queuing is enabled, any new instance of a data job (such as OCPM) that is scheduled to start while a previous instance is still running will be placed in a queue and start once the previous run completes.

With queuing currently disabled, any overlapping or simultaneous data job runs will be skipped, as per the previous system behavior.

We’ll provide updates as we work to restore the queuing feature. Thank you for your patience and understanding.