You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When cromshell server is busy, sometimes the workflow takes a while to be registered. cromshell wait will fail 2/3 times. Instead, it should wait even when the jobid is not found till the job actually started running.
louisb: "I believe it the thought behind -w was that when you're developing wdls and launching them manually there's a very high chance of a fast error because of wdl validation failure or bad input arguments. You want to find out if that happened before you continue on with your work."
The text was updated successfully, but these errors were encountered:
https://docs.google.com/document/d/1c8m9Ks4jgc_11ftC4_NU4XEe7BkY_ghwcy9Oj3eEfzY/edit?usp=sharing
When cromshell server is busy, sometimes the workflow takes a while to be registered. cromshell wait will fail 2/3 times. Instead, it should wait even when the jobid is not found till the job actually started running.
louisb: "I believe it the thought behind -w was that when you're developing wdls and launching them manually there's a very high chance of a fast error because of wdl validation failure or bad input arguments. You want to find out if that happened before you continue on with your work."
The text was updated successfully, but these errors were encountered: