Fatal: No reads found in input.
As a guess, was the correct dataset input to the tool? You can review this for any job using the pencil icon → details tab on one of the output datasets.
For more specific help, would you like to share back your history? FAQ: Sharing your History. You can paste back the link to the history here in a reply. Then, once we are done, toggle the sharing off.
Screenshots can also sometimes work but you’ll need to capture details like the server, the tool version, the inputs, and the full job logs. For how to do this, please see → How to get faster help with your question
Let’s start there! 
Hi, please use the link above.
please use the link below
https://usegalaxy.eu/u/priyasamson/h/l3-summer-1-1-2-1-1-2
From the top level it appears that the input dataset was empty when the job was submitted. This can happen when datasets are deleted while the job is still executing. I’d like to confirm this and other details since I’m guessing that isn’t what actually happened?
I’m having trouble reviewing your history due to the size. Would you please try this:
- Copy just that original input collection into a new history.
-
Start up the job again by inputting the entire collection.
-
Post back a link to that new history as a reply. It is Ok if it is still running. This is our rerun test and I’ll watch it process, see any new errors that may be generated, and be able to inspect the run details easier.
-
Then we can follow up until this is resolved.
Thanks for your patience! You can continue to work in your other history, or decide to split off your work into other new histories.
Copies of data within your own account do not consume extra quota space, and working in several histories is a great way to keep work organized! It also is useful sometimes to get rid of all the older records of deleted data. Galaxy can handle it fine, but web browsers start to have trouble with the display of all those details after the first few thousand or so records.
For a quick way to refresh, consider creating a copy of your history. If you use the default settings, old deleted data will be left behind, and only the currently active and hidden datasets will be cloned over. You can edit that original history name in a meaningful way “Old history ABC” and start working in the new cleaner copy version. Then, later on, you can consider deleting/purging any marked “Old” but you don’t need to worry about that right away since it isn’t taking up any additional space. FAQ: History options
Hope this helps and I’ll watch for your reply! 
Hi @jennaj,
Thank you for the details, I will create a copy of the data and post the link.
much appreciated