Run_workflow is synchronous? about bioblend

[dannon]

Are you sure that control is held until all datasets are completed? Or is it just until scheduling is done? (see response to your message on galaxy-dev)

While it must wait until scheduling is complete (for now), bioblend should not be waiting until all workflow jobs are complete with wait=False.

[bollig]

I think in this case Galaxy is holding the connection open until it feels scheduling is complete. For 100+ steps, the scheduling took about 2 minutes and I let the connection remain open for another 30 minutes before raising an interrupt.

[simleo]

Yes. Without wait the method returns after scheduling, while with wait it returns after the workflow is complete (i.e., no output dataset is in a "pending" state). The operation is actually blocking in both cases, the only difference being the amount of time it takes to return control to the caller. We should update the docs to clarify this. Thanks for reporting!

[simleo]

Docs updated as of 3ec511c

[jmchilton]

Also @bollig for what it is worth - workflow scheduling taking to long is a known problem and @dannon and I are working on different aspects of fixing that (e.g. https://bitbucket.org/galaxy/galaxy-central/pull-request/453/rfc-workflow-requests-api-only-and-a/diff). There will hopefully be relief with the next version of Galaxy (or if not the following one).