Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Got a problem?

1. Search using the upper-right search box, e.g. using the error message.
2. Be as detailed as you can when describing your problem, i.e. tell us what happened or didn't happen rather than "it didn't work" or "it failed".
3. Include the full text of any error messages you encounter.
4. Include relevant code snippets in the body of your post (see formatting tips below) and attach your full WDL script using the "Attach a file" link below the comment box.
5. Tell us what version of Cromwell, wdltool or any other software involved you are using.
6. Tell us what platform you are running on.

Get email notifications!

You can opt in to receive email notifications, for example when your questions get answered or when there are new announcements on the blog, by following the instructions given here.

Formatting tip!

Wrap blocks of code, error messages and BAM/VCF snippets--especially content with hashes (#)--with lines with three backticks ( ``` ) each to make a code block as demonstrated here.

Jump to another community

Update: July 26, 2019
This section of the forum is now closed; we are working on a new support model for WDL that we will share here shortly. For Cromwell-specific issues, see the Cromwell docs and post questions on Github.

Starting to see some weird errors in PAPI

ebanks Broad InstituteMember, Broadie, Dev ✭✭✭✭

March 1 in Ask the Cromwell + WDL Team

I have hundreds of jobs dying with:
"Task gnarlyPipeline.HardFilterAndMakeSitesOnlyVcf:44:1 failed. The job was stopped before the command finished. PAPI error code 3. Invalid value for field 'global': 'global'. Unknown global."

I'll note that this has affected ~10% of my running jobs, but the other 90% (within the scatter) all finished fine.

0 ·

or Register to comment.