-
Bug
-
Resolution: Done
-
Critical
-
None
-
1.4.0
-
False
-
-
False
-
-
Description of the problem:
**
The "Run has failed" message generated when workflow goes into error should not appear after retriggering the workflow from the failure point and the workflow completed successfully.
Additional info from dev:
The error message is sent by the DataIndex (so unrelated to the completedWith or similar).
The state is Completed (not Error as would be expected in this case).
In other words, the UI is receiving confusing data from the DataIndex.
How reproducible: 100%
Steps to reproduce:
1. Deploy orchestrator 1.4.0-rc11
2. Deploy workflow like MTA 1.4.0-rc5
3. Edit the workflow props configmap to lose access to the mta inner service. The workflow should fail with Error status in the UI.
4. Restore the correct URL in the MTA props cm and retrigger the workflow in the UI from the failed point.
Actual results:
**
The workflow completed but the "Run has failed" message still appears in the Results pane, even though you see in the Workflow progress + results output that it completed successfully:
![]()
![]()
Expected results:
I would expect the "Run has failed" message to go away after the retrigger and workflow completion
- relates to
-
FLPATH-2130 Result error status should be removed after successful retrigger
-
- Closed
-