6 months ago by
United States
Hello,
The developers are still looking at the problem and we consider this a priority fix. I created a ticket specifically for this problem (using a simpler tool, but one that presents with the same behavior), please follow for updates: https://github.com/galaxyproject/usegalaxy-playbook/issues/125
Thanks for reporting the problem! And definitely try the "rerun" workaround as not all submitted jobs with multiple selects end up in this state (we are not exactly sure why yet).
Thanks for reporting the problem! Jen, Galaxy team
Hi - I've seen similar behavior with other tools with multiple-select inputs over the last week. I haven't run into it today. I'll do some more testing and open a ticket for the developers to review/fix. Because of this, I don't think the problem is with
cxb
data, but I'll test that too.Meanwhile, I had success before even with this problem going on by rerunning the job (actually using the rerun button), choosing the inputs again, and executing the job. In some cases, it took a few attempts. You can always permanently delete the jobs that didn't capture all the inputs - you can usually tell even while the job is queued by the dataset name (includes a list of the inputs by dataset number). Only so many datasets can be listed, so this is of limited use if there are several inputs (more than 3 or 4), but might help.
Thanks for reporting this and more feedback very soon. Jen, Galaxy team