-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
Retriggering workflows
-
False
-
-
False
-
In Progress
-
0% To Do, 0% In Progress, 100% Done
-
-
In M2 we had to drop the retriggering action from the UI (see FLPATH-1655) since the OSL-1.33 runtime image had a bug that prevented it from working.
In M3, switching to OSL-1.34 runtime, the issue was resolved. For that purpose, the feature can be revived.
- depends on
-
FLPATH-2135 After retriggering a workflow from failure point, no clear indicator to user that workflow is still running
-
- Closed
-
-
FLPATH-2136 Retriggering at failure point adds another failed node step to workflow progress section
-
- Closed
-
- is related to
-
FLPATH-1655 After retriggering a workflow that was in Error, workflow state remains in Error
-
- Closed
-
- links to