Add "Check my connectivity" function for troubleshooting compute environments
evaluating
Rob Newman
evaluating
Updating to new status
Drew DiPalma
under review
Rob Newman
Merged in a post:
Workflows hang with incorrect Azure credential (need error trapping)
A
Alloy Hare
Nextflow version - 23.08.1-edge build 5874
While onboarding a new user to our Seqera Platform Enterprise server and setting up the Azure credential, we mistakenly put the batch account name in the "Blob Storage" account name.
The result was they could launch the
Hello World
Nextflow pipeline, but the workflow would just hang with no error report or execution log. The user interface indicates that the workflow is still in progress (forever). This is challenging because the user has no indication of the error root cause. If they were starting with a real workflow rather than Hello World
, they might suspect the Nextflow version or the configuration. Two improvements would help resolve this:
- Credentials should be tested at the time of credential creation
- Trap Nextflow errors that occur before the blob storage is established
Note: I don't know if this is already handled for non-Azure executors (such as AWS or GCP).
I am attaching the Nextflow log file to assist you.