Fix engine error handling
Error handling model is not clear now because we may do TX rollback in situations when we should just change a corresponding execution object and commit a transaction. For example, YAQL errors in on-success/on-error clauses must not lead to TX rollback (it is fixed but requires more testing). So we need to find a unified approach for this.
Blueprint information
- Status:
- Complete
- Approver:
- Renat Akhmerov
- Priority:
- High
- Drafter:
- Renat Akhmerov
- Direction:
- Approved
- Assignee:
- Renat Akhmerov
- Definition:
- Approved
- Series goal:
- Accepted for newton
- Implementation:
-
Implemented
- Milestone target:
-
newton-2
- Started by
- Renat Akhmerov
- Completed by
- Renat Akhmerov
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Fixing engine facade hierarchy
Addressed by: https:/
Refactoring exception hierarchy
Addressed by: https:/
WIP: engine refactoring
Gerrit topic: https:/
Addressed by: https:/
Refactoring workflow handler
Addressed by: https:/
Add explicit preconditions for methods of Action, Task and Workflow
Addressed by: https:/
Removing redundant wf_ex_id parameter for rerun across the code
Addressed by: https:/
Add more tests for error handling
Addressed by: https:/
Add error handling tests: invalid workflow input, error in first task
Addressed by: https:/
Add proper error handling for task continuation
Addressed by: https:/
Add proper handling for implicit task completion
