Glad you got it working, and thanks for the additional information. Now that I
know what's different about the non-working workflows I can probably recreate
and fix this on my end. Extracted workflows *should* function via the API.
-Dannon
On Jan 9, 2012, at 5:06 PM, Leon Mei wrote:
> Hi Dan
Hi Dannon,
Thanks for the hint. I got it working by removing "input dataset" step and
adding it back in the workflow canvas. The previous workflow in question
was purely extracted from history.
So now I can check the details via API:
./display.py
http://galaxy.nbic.nl/galaxy/api/workflows/e037f
Leon,
I'm not seeing this behavior in any of my instances. I assume they work
correctly through the standard galaxy interface, but is there anything special
about the workflows in question? Is there perhaps a tool with no inputs in use?
Thanks!
-Dannon
On Jan 6, 2012, at 11:59 AM, Leon M
Hi,
I received an error when I was trying to view the details of existing
workflows through API.
I can see 4 workflows owned by myself successfully. But viewing the details
of any workflow got me a 500 error.
./display.py http://galaxy.nbic.nl/galaxy/api/workflows
Collection Members
--
