[MGRENTITLE-2] CO - mgr-tenant-entitlements - Implement handler for skipped flows Created: 31/Dec/23 Updated: 31/Dec/23 |
|
| Status: | Open |
| Project: | mgr-tenant-entitlements |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Craig McNally | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | back-end, epam-eureka, eureka-phase4, need-review | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Eureka | ||||||||
| Description |
|
Every entitlement flow entity is created before actual flow execution with status QUEUED, and marked as finished/failed/canceled/cancellation_failed status on flow finish. With hierarchical application installation, it leads that if flow at Level 1 fails, the application on Level 2 is marked as skipped and it should be processed outside of the flow context using try-catch or flowFuture.onError() for async execution. To avoid it - the flow engine can be extended with onFlowSkippedStage() method to perform some action if the flow was skipped. |