pylabrobot.opentrons.flex.Flex.create_run

async Flex.create_run() → None

Start a control session.

The robot reports itself as in use and refuses its own touchscreen for as long as a run is current, so this is the step that takes it from the operator, not connect. Cancels a run this object already holds first; run_id is the only handle on a run, so overwriting it would strand the old one on the robot with nothing left able to release it.

labwareIds and uploaded definitions are both run-scoped server-side, so a new run must not serve cached identities from a previous one.

Return type:

None