Control state transitions of tasks and flows
Registered by
Ivan Melnikov
Tasks and flows have states (PENDING, RUNNING, SUCCES, FAILURE, etc). We should document what states and transitions are possible and enforce that in code.
Blueprint information
- Status:
- Complete
- Approver:
- Joshua Harlow
- Priority:
- High
- Drafter:
- Ivan Melnikov
- Direction:
- Approved
- Assignee:
- Ivan Melnikov
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Joshua Harlow
- Completed by
- Joshua Harlow
Related branches
Related bugs
Sprints
Whiteboard
imelnikov: I started a wiki page to document states: https:/
Addressed by: https:/
Validate each flow state change
Gerrit topic: https:/
Addressed by: https:/
Update state sequence for failed flows
(?)
