Capture Batch retries in Seqera Platform logs
acknowledged
I
Indigo Marmot
It would be very helpful to see which Tasks in a Workflow were restarted in AWS Batch, e.g. due to spot-instance termination. In our specific case we had a few relatively long-running Tasks, which were restarted frequently on Batch, leading to much longer runtime (and higher compute cost) for the Workflow. But there was no notification in the Seqera Platform of this problem. In fact, the standard Task log output (stdout / stderr) in Seqera Platform/Tower gets 'stuck' on the first run of the Task. It doesn't show anything from the restart attempts.
Rob Newman
acknowledged