Introducing a new run state - READY

This is a quick note to let you know that on the 4th of September we’ll be introducing a new run state - “READY”.

This is an automatic migration that doesn’t require any additional input from your side, but it will change the run state progression. Runs will now progress from state “QUEUED” to the new state “READY”.

The goal of this change is to add additional clarity to the run progression. Moving forward, the “QUEUED” state will mean that a run is not ready for scheduling, as it’s either blocked, waiting for dependencies to finish, or isn’t approved. The “READY” state will mean that a run is ready for scheduling and is waiting for a worker to pick it up.

Feel free to reach out to us if you have any questions or concerns.