EXPERIMENT 002 · orbit
execution states
trying the transitions Orbit allows — and the ones it rejects
Question
Which operations does each state accept, and what does a rejected one look like? An interactive representation of Orbit’s current Execution domain rules. State changes happen in this browser example: no commands run, and there is no scheduler behind the page.
Bench
bench · simulated in this browser
QUEUEDstart →RUNNINGsucceed / fail →SUCCEEDEDFAILEDcancel from queued or running →CANCELLED
Sample execution. Try an operation, including one this state rejects.
Accepted now: start, cancel. Rejected now: succeed, fail.
Solid buttons are accepted. Dotted buttons remain clickable to show the rejection.
State
- status
- QUEUED
- startedAt
- —
- finishedAt
- —
- exitCode
- —
- errorMessage
- —
Times come from this browser’s clock.
History
- created → QUEUED
| action | from | to | sets |
|---|---|---|---|
| start | QUEUED | RUNNING | startedAt |
| succeed | RUNNING | SUCCEEDED | finishedAt, exitCode |
| fail | RUNNING | FAILED | finishedAt, exitCode, nonblank errorMessage |
| cancel | QUEUED · RUNNING | CANCELLED | finishedAt |
Fidelity
transition rulesported from orbit cd97666
commands, schedulernone
persistencenone · reload starts over
retry and timeoutconfiguration only, not exercised
Based on Orbit revision cd97666. Timestamps are browser-generated sample values, with no persistence. Retry and timeout settings are configuration only.