Actions
Bug #13772
open
Rerunning a container_request that has a failed child CR should restart the failed CR
Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
-
Release:
Release relationship:
Auto
Description
I had a CR that had one running child, one Complete child, and one Failed child. When restarted, the top level workflow runner reused itself, so the Failed job did not rerun. I want to keep the progress on the running job so I'm not sure what's the best answer here.
My example: e51c5-xvhdp-8xntw7j6soelqej was run first, then e51c5-xvhdp-1a3v37qei94y8fk was run (check created_at times).
Updated by Tom Clegg over 5 years ago
- Related to Feature #13773: "Will fail" status for failing (but not yet failed) containers added
Updated by
Actions