Galaxy won't let me edit attributes even though fastq file is not in use. I'm trying to change to fastqsanger and when I click save it comes up with an error message saying: This dataset is currently being used as input or output. You cannot change datatype until the jobs have completed or you have canceled them.
I've deleted the job and tried refreshing the browser.
Any ideas?
Hello,
This is a strange one.
First try refreshing the history - do this by clicking on the round double arrow at the top of the right panel.
Second, maybe try logging out then logging in again. Just curious if this works or not (probably won't. Would be good to let us know if it does. I am not sure how much can be done to replicate the problem, but sending the email address of your account along with the dataset number will give us a chance to take a look.
I haven't ever had this happen, or not prior reports of this issue have come up before.
If none of this works, you can also send the email/dataset info and we can take a look. It might be best to send this to our list galaxy-bugs@bx.psu.edu for privacy.
Hope the first one works, but keep us posted. Jen, Galaxy team
ps: I forgot to ask if you were working on the public Main Galaxy instance. If not, then troubleshooting will need to be done with the administrator of the instance you are working on. They can also ask for help on the galaxy-dev@bx.psu.edu mailing list (has more visibility to development team & community).
Hi Jen,
I am using public. I tried both suggestion without any luck. I had tried to run map with bowtie without changing the file datatype from fastq to fastqsanger. I then deleted that operation and since then haven't been able to change its datatype. I have been able to change it for my other fastq files for which I did not run bowtie until I had their their datatype.
Thanks.
Hello,
If the dataset is being used for any tool/function, then metadata cannot be changed until all dependencies have completed. Deleted datasets may take a bit to be completely quit out of. Sometimes permanently deleting helps then to clear up quicker. The jobs should be in the failed state after it quits out (not yellow running. or grey waiting to run).
Please try again now, enough time has passed.
If this this is still occurring after 19 hours from when the Bowtie job was deleted (then perm deleted), we'd like to know about it and the conditions. Sharing your account info will help with this. We want to capture and fix any underlying issues around this behavior if it turns out to be novel.
Please include the dataset numbers for the fastq datasets with the problem plus the linked Bowtie job (although I will be able to tell which Bowtie job was linked from the input fastq datasets, I want to be certain we are looking at the same data in your history)
Best, Jen, Galaxy team
Thanks. I ended up deleting the files and uploading them again. That fixed it.
That is another way to do it. My guess is that you tried to edit metadata right after deleting the Bowtie job, and it was too soon, the job had not resolved as "quit" yet.
Thanks for sending the update. You can ignore the last post I put out a minute before your reply (didn't see it while typing the post), but perhaps it will help next time, and others reviewing prior Q&A here that are troubleshooting the same issue.
Thanks! Jen, Galaxy team
