HomeThe workflow lifecycle lab
A request has a life after send.
Inspect each state, then decide what counts as finished.
INTERACTIVE FIELD GUIDE / 01Follow the work.
SIMULATED DATAFollow the work.
Find the failure.
One approved article. Six possible paths. Step through what happens between a request and a verified page.
NO SERVICES CONNECTED
All checks succeed. Completion requires the expected revision and canonical at the destination.
- 01Validate inputWaiting
- 02Check approvalWaiting
- 03Submit requestWaiting
- 04Resolve operationWaiting
- 05Verify destinationWaiting
- 06Record receiptWaiting
EXECUTION RECORD0 / 6 steps
READY
Start with a defined result.
The example will check article A-014, revision 12. No request will be sent.
- ARTICLE / REVISION
- A-014 / r12
- CREATE ATTEMPTS THIS RUN
- 0
- FINAL RECEIPT
- Not issued
Inspect the step history
- No steps run yet.
A learning model with invented records and responses. It does not connect to your accounts, execute a workflow or promise a provider’s retry behavior. Inputs and progress are not saved.
Why accepted is not completed ↗