Surface failure-to-start error messages at the task level
Rob Syme
A task may fail to start if the container pull timeout is exceeded, for example. If the user has a task retry policy configured, Nextflow will re-submit the task to the queue. The task table shows no exit status (correctly), but does not offer information to suggest that the task did not succeed or why. This information is available in the Nextflow logs, but those logs won't be available until the run completes.
It would be helpful if Platform displayed diagnostic and debugging information about tasks that fail to start.