Scheduled Maintenance Expected to Temporarily Increase Latency

What are we doing?

We will be running a backend migration of how job numbers are generated starting at 08:00 UTC on the 21st of June and running for up to 2 hours.

During this time window, there will be up to 5 periods of increased latency for starting jobs and workflows. Each period will last for 2 to 3 minutes.

Jobs that have already started running won’t be affected.

Delayed workflows will be started/continued when each phase of the migration has completed.

Why will there be increased latency?

In order to maintain consistency of job numbers, we are taking the precaution of reducing concurrency in our workflows system during this migration. Concurrency will be reduced for the minimal amount of time necessary to run a phase of the migration.

Why will there be up to 5 periods of increased latency?

We will be migrating projects in multiple phases. There is a gap between each phase for monitoring, and to clear any backlog of delayed jobs and workflows.