Store failed and hospitalised errors along with corresponding statuses

Description

Below are some thoughts on how to implement this but I have not been able to think of a good solution without writing code for it.

  • FAILED when a flow fails exceptionally. See TopLevelTransition.errorTransition and TransitionBuilder.errorsTransition. This status will require new actions (or reuse existing actions but a new transition must be created) to be added as it will require a new database transaction and commit. Before creating the new transaction, the previous transaction must first be rolled back. Need to double-check this implementation.

  • HOSPITALIZED when a flow goes to the hospital and is kept in for observation. See TopLevelTransition.errorTransition and TransitionBuilder.errorsTransition. This status will require new actions (or reuse existing actions but a new transition must be created) to be added as it will a new database commit. The flow must then not disappear into the ether and continue to process the next actions.

Both failed and hospitalised flows will require the exception that caused the error to be saved to the database.

Assignee

Kyriakos Tharrouniatis

Reporter

Dan Newton

Labels

None

Sprint

None

Priority

High

Engineering Teams

Kernel - Flow State Machine

Fix versions

Affects versions

None

Story Points / Dev Days

5

Build cut

None
Configure