Error Report(rawls... 400 Bad Request) when accessing some Sample Sets while others are unaffected
Hello team,
I'm working with an rnaseq workflow calling genes of interest against GTEx data , and I've encountered a problem when aggregating results , where I read in a sample_set of results to aggregate , where some sample_sets are read in just fine and other generate an incredibly cryptic error, starting with:
ErrorReport(rawls,HTTP error calling URI...)
I've just gone ahead and re-linked my NIH authorization, and this still happens. I've got sample sets of sizes 1000, 2382, 5000, and 5000 entries - only the latter two throw this error. When I ran this workflow in August, I don't believe I encountered this error, and neither did the person before me in my role. Would you be able to help , have any idea on how to fix this myself , or have any more information on the error message ? Thank you for any help you'd be able to provide!
This is the workflow linked down below:
(Source: broadinstitute_gtex/rnaseqc2_aggregate_results_v1-0_BETA/3)
Comments
2 comments
UPDATE: I've had some luck by splitting the samples into smaller sets (3000 seems to work just fine), thanks to some guidance on some previous forum posts and the super useful option for doing that on your website UI, but I'm still curious to learn more about what's up with this error and how to interpret it if it comes up again in the future
I just encountered this issue too. A colleague confirmed my fear: the length of the input JSON was too long for Terra to be able to submit the job (which fits with your observation that the error went away with smaller sample sets). In my case I can't change the size of the sample sets, so I'm going to try creating files containing the strings and file paths I was trying to supply as arrays. This is definitely a hassle!
Please sign in to leave a comment.