After the latest upgrade (april), I'm having issues when starting (batch) workfows. Sometimes, it seems that step dependencies are not stored correctly, leading to some steps being started too soon, without prior datasets being completed. Specifically, for some workflows, some of the later steps start immediately. The issue seems to be random: in batch workflow submission, some run flawlessly, others show the issue, at different steps. I use one handler in the job_conf to exclude race conditions and shared variable clashes.

I suspect there is an issue with fetching or storing the steps to/from the database (a remote mysql database in my case). On the mysql-side there are no errors in the log files, and the galaxy-logs don't show clear issues either.

Does the job new job handler check for failed database connections? If not, could somebody point me to the code that performs these steps, I'd like to add a check & retry routine to see if this improves the situation.




Geert Vandeweyer, Ph.D.
Department of Medical Genetics
University of Antwerp
Prins Boudewijnlaan 43
2650 Edegem
Tel: +32 (0)3 275 97 56
E-mail: geert.vandewe...@ua.ac.be

Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

To search Galaxy mailing lists use the unified search at:

Reply via email to