Hi, My rather large files have been running on EggNOG since 9 April. It is not complete yet. Can you help check if something else is wrong or the tool is queued up?
Welcome @Anwesha_Ghosh
Oh! That does seem too long.
Which server are you working at? Would you like to share a link to the history with the run so we can help to figure out what might have been the problem? How to share for feedback is in the banner of this forum, also here →
If you are not sure how jobs process, the color of the dataset will indicate the status. Maybe helpful? The gray color is the queued state, and yellow means executing. Two weeks for either state would be very unusual, so this part is help for later, not now.
Let’s start there, thanks! 
Hi,
I am on usegalaxy.eu
Link to one of the jobs https://usegalaxy.eu/datasets/4838ba20a6d86765fe9bfe8eb44b5757/details
You will need to set the history to a shared state for us to be able to see the details for a job. Then, if you share the history itself, we might be able to offer more feedback based on the inputs to the job. Thanks!
Hi Jennifer,
I have a lot of data on the history where the file is running. Can I share a screenshot with all relevant information? Would that work ?
1 Like
Yes, we can try that first. Go into the job details view using the i-icon.
The parameters up at the top will help. You can also expand the datasets – just the first few lines will be shown with the datatype format and database assignments (if any). Then scroll down into the runtime details. There will be a “job api ID” – be sure to capture that. Then we can ask the EU administrators for more help using that as needed.
Let’s see how far we can get. I mostly just want to check the job state and the timestamps, plus check the job state, and state of the inputs. Why a job is delayed depends on a few factors and server hiccups are possible (rare but the EU server had some changes recently, maybe some rerun was missed).
Dataset Information
Number | 106 |
- | - |
Name | eggNOG Mapper on data 66: annotations |
Created | Monday Apr 14th 23:16:23 2025 GMT+5:30 |
Filesize | - |
Dbkey | ? |
Format | tabular |
File contents | contents |
History Content API ID |
4838ba20a6d86765fe9bfe8eb44b5757
|
History API ID |
116feafc47628329
|
UUID | 802d104e-0aed-4d31-8906-28b6da7a724b |
Full Path | /data/dnb11/galaxy_db/files/8/0/2/dataset_802d104e-0aed-4d31-8906-28b6da7a724b.dat |
Originally Created From a File Named | results.emapper.annotations |
Tool Parameters
Input Parameter | Value |
- | - |
Version of eggNOG Database | 5.0.2 |
Basis for annotation | diamond |
Fasta sequences to annotate |
|
Type of sequences | metagenome |
Translate predicted CDS from blastx hits to proteins | false |
Type of sequences | Inferred from Diamond/MMseqs2 blastx hits |
Scoring matrix and gap costs | BLOSUM62 |
Gap Costs | Existence: 11 Extension: 1 |
Diamond’s sensitivity mode | sensitive |
Run diamond in iterative mode, up to the sensitivity level | false |
Ignore Diamond warnings on sequence content (e.g. when a protein contains only ATGC symbols) | false |
Minimum query coverage | Not available. |
Minimum subject coverage | Not available. |
Minimum query coverage | Not available. |
Minimum query coverage | Not available. |
Minimum query coverage | 0.001 |
Annotate seed orthologs | |
Min E-value threshold | 0.001 |
Minimum bit score threshold | Not available. |
Set taxonomic scope | Not available. |
target orthologs for functional transfer | all |
Select the set of GO terms that should be used for annotation | non-electronic = Use only non-electronically curated terms |
output_options | |
Exclude header lines and stats from output files | true |
Output a file with the list of orthologs for each hit | false |
Add md5 hash of each query to annotations | false |
Job Outputs
Tool Outputs | Dataset |
- | - |
eggNOG Mapper on : seed_orthologs |
|
eggNOG Mapper on : annotations |
|
Job Information
What was posted back isn’t enough information for me to see what is going on.
The EU team might be able to help if you can post back everything from that last sections (where the job API ID is located). They will see this when they are back again on Monday if you want to post before then.
Do you have an update?
How to generate a share link to your history is in this FAQ → FAQ: Sharing your History
The alternative is to copy and paste the entire job details view. You pasted back some of the details from the top of the page but the details in the middle and last section is what will allow others to help.
Your job is taking much too long to process and we would like to help! I can start up a private chat to share the link in instead? But we would still need to bring in other people from the EU team to inspect. I’ll start the chat up in case you want to try that way instead.