I tracked down this issue to a bug in the workflow export code, and I've fixed
it. The fix will appear on our public server early next week; please let us
know if you're still seeing this error late next week.
On May 23, 2013, at 9:50 AM, Andreas Kuntzagk wrote:
> For the first of the CloudMap workflows that worked. But the second failes
> with this error message:
> Failed to open URL:
> Exception: HTTP Error 500: Internal Server Error
> I don't see any information in the log files.
> regards, Andreas
> On 22.05.2013 13:57, Dannon Baker wrote:
>> On Wed, May 22, 2013 at 3:12 AM, Andreas Kuntzagk
>> <mailto:andreas.kuntz...@mdc-berlin.de>> wrote:
>> But how do I get the workflow_id? For example for the workflow
>> what would the workflow_id be?
>> (I tried "cloudmap-unmapped-mutant-__workflow-no-candidates" but this did
>> not work.)
>> If you click on that link above, you can see the id in the url for the
>> 'Import' link. Again,
>> definitely not optimal -- public workflows should probably all be exposed
>> via the API for use/import.
> Andreas Kuntzagk
> Berlin Institute for Medical Systems Biology at the
> Max-Delbrueck-Center for Molecular Medicine
> Robert-Roessle-Str. 10, 13125 Berlin, Germany
> 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:
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: