-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
True
-
-
False
-
-
Currently, when an user wants to abort a workflow execution, there is no pre-check to ensure the process execution actually exists on the workflow's pod.
If the workflow pod is delete, the process execution will never be there and an error will occurs 100%of the time.
So, the abort button should be disabled/hidden if the workflow execution does not exist in the current workflow pod.
In general, we may even wants to update the state of the workflow execution
- depends on
-
SRVLOGIC-257 SonataFlow Gateway API Research Spike
- New
- is depended on by
-
FLPATH-962 Backstage plugin fails to update catalog when workflow SF is deleted
- Closed
- relates to
-
FLPATH-1062 [Orchestrator UI] - MTA workflow runs for 1 hr with invalid inputs
- Closed
-
FLPATH-1148 [Orchestrator] - workflow stuck in active state if workflow pod is deleted during workflow execution
- Closed