I see the bug you're running into. As a temporary solution, executing workflows via the API with 'no_add_to_history' in the payload should work as expected. I'll have a permanent fix out shortly.
-Dannon On Jul 5, 2012, at 5:12 PM, Thon Deboer wrote: > Hi, > > I am continueing to struggle with the API.... > > I have created a workflow execution engine that submits a workflow using the > examples in the API (scripts/api). > > When I run the WF on data in the LIBRARIES everything works fine. > But when I choose a HISTORY as my source of data, the WF executes fine, but > the history I use is emptied of all the files in there! > > This is very bizarre....Any ideas what is going on here? > I know not a lot of people are using the API, but it is the only way I can > run paired end WF on more than a couple of samples... > > Regards, > > Thon de Boer, Ph.D. > Bioinformatics Guru > +1-650-799-6839 > thondeb...@me.com > LinkedIn Profile > > > > > ___________________________________________________________ > 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: > > http://lists.bx.psu.edu/ ___________________________________________________________ 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: http://lists.bx.psu.edu/
