What happens to each
A cancellation is carried out. So is a change, unless the account is on hold or has failed: each change is then put back for a later pass, while cancellations still run.
Pausing an account is set from outside. The worker reads that setting and never changes it.
What the ordering means
A cancellation already in the line is carried out before the next piece of submitted work starts. One arriving after the line is emptied waits for the next pass.
Related
Source evidence
---
row: P1-08
baseline: 49aa659
created: 2026-09-23 08:19 UTC
modified: 2026-10-11 19:29 UTC
evidence:
- claim: "The line is emptied every pass once the account has started"
source: "`execution_manager.py` 3910-3911, unless a still-starting account stops at 3903-3905"
- claim: "A cancellation taken from it is carried out"
source: "`execution_manager.py` 3940-3941"
- claim: "A change taken from it is carried out too"
source: "`execution_manager.py` 3938-3939"
- claim: "A held or failed account puts each change back instead"
source: "`execution_manager.py` 3913-3920, returned at 3953-3954"
- claim: "Holding is a flag set through a call of its own"
source: "`execution_manager.py` 3281-3286"
- claim: "The worker reads it when deciding whether to defer a change"
source: "`execution_manager.py` 3914"
- claim: "It reads it again before taking new work"
source: "`execution_manager.py` 3969"
- claim: "The line is emptied before any submitted work is taken"
source: "`execution_manager.py` 3910-3911 ahead of 3980-3984"
- claim: "A still-starting account reaches neither"
source: "`execution_manager.py` 3903-3905"
---