Todd, Errors when importing history archives are not exposed well right now. If you look at the job table in your Galaxy database, you should be able to see why the job failed. Using SQL like this should work: -- select * from job where tool_id='__export_history__' order by id desc limit 5; -- Alternatively, can you share a history archive that's failing and we can take a look? Thanks, J. On May 29, 2012, at 2:42 PM, Todd Oakley wrote:

Hello, I want to be able to analyze data on one Galaxy instance, and store histories more permanently on another. This is critical for us as we have storage usage limits on the shared machine with the most computational power.

Although I am now able to export histories as a file, I cannot import histories.

When I choose under history "Import From File", I get a message saying the history is importing and will be visible when finished. However, I never see the history. I've tried many combinations with different histories - saving and downloading in the same Galaxy instance, downloading on one instance and importing on the other, saving the file in a different location altogether or using the link provided in export history.

I've not been able to import a history from a file.

Thanks for any advice.

Todd --

*************************************** Todd Oakley, Professor Ecology Evolution and Marine Biology University of California, Santa Barbara Santa Barbara, CA 93106 USA ***************************************

___________________________________________________________ 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/