Check FAQ: Functional Mapping and Annotation of Genome-wide association studies
Search Google user groups for similar errors to see if this issue has been answered before: FUMA GWAS users - Google Groups
Read and re-read FUMA tutorial: Functional Mapping and Annotation of Genome-wide association studies
Post questions/issues on Google user group
File upload failed.
This error is because your file upload failed. Please try again. Do not leave the page while uploading the file (after clicking the submit button).
Only click the "Submit Job" once.
Try using a different browser and/or hard refresh the page. (Ctrl + shift + r)
Try using a VPN.
Try a personal computer from a home network. (Sometimes networks in working environments are very strict)
The input file format was not correct.
Please make sure your input file has sufficient column names.
rsID if exists has to be in rsID format. See tutorial.
Compress the raw file using the .gz extension.
The chromosome has to be numbers between 1 and 23 or X.
Position values have to be integer (not in scientific notation).
Please refer Tutorial for details.
ERROR magma:This error can occur if the rsID and/or p-value columns are mistakenly labelled wrong.
Please make sure your input file has the correct column names.
Please refer Tutorial for details.
Error during SNPs filtering for Manhattan plot. This error can occur if the p-value column is mistakenly labelled wrong.
Please make sure your input file has sufficient column names.
Please refer Tutorial for details.
ERROR 005:Error from lead SNPs and candidate SNPs identification / No significant SNPs were identified.
This error can occur when no candidate SNPs are identified. Note that indels are included in the FUMA from v1.3.0 but both alleles need to match exactly with the selected reference panel.
MHC region is also excluded by default.
If there is no significant hit at your defined P-value cutoff for lead SNPs and GWAS-tagged SNPs, you can try to use a less stringent P-value threshold or provide predefined lead SNPs.
If there are significant SNPs with very low minor allele frequency, try decreasing MAF threshold (default 0.01).
Manhattan plots and significant-top 10 SNPs in your input file are available from SNP2GENE.
ERROR 006:Error from lead SNPs and candidate SNPs identification. This error can occur because:
invalid input parameters or
columns are mistakenly labelled wrong.
Please make sure your input file has the correct column names.
Please refer Tutorial for details.
ERROR 007:Error during SNP annotation extraction. This error can occur because:
invalid input parameters or
columns are mistakenly labelled wrong.
Please make sure your input file has the correct column names.
Please refer Tutorial for details.
ERROR 008 - 009:Error during extracting external data sources. This error can occur because
invalid input parameters or
columns are mistakenly labelled wrong.
Please make sure your input file has the correct column names.
Please refer Tutorial for details.
ERROR 010:Error from chromatin interaction mapping. This error might be because one of the uploaded chromatin interaction files did not follow the correct format.
Please refer Tutorial for details.
ERROR 011:Error during gene mapping. This error can occur because:
Invalid input parameters or
columns are mistakenly labelled wrong.
Please make sure your input file has the correct column names.
Please refer Tutorial for details.
ERROR 012:Error from circos. This error is most likely due to server-side error. Please contact the developer for details.
ERROR celltype:An error occurred during the process of your cell type specificity analyses. Please make sure that your provided inputs meet all the requirements and check the following:
Does your selected SNP2GENE job have MAGMA output? If you can see manhattan plot for gene-based test, this should not be the problem.
Is your uploaded file an output of MAGMA gene analysis with an extension "genes.raw"?
Does your file contain Ensembl gene ID? Otherwise, don't forget to UNCHECK the option to indicate that you are using Ensembl gene ID.
If any of those don't solve the problem, please contact to the developer.
ERROR timeout:This error occurs when the system's processing time limit (8 hours) for a specific task or operation is exceeded. It often indicates that the system was unable to complete the task within the expected timeframe, possibly due to heavy load. Users encountering this error may need to retry the operation later or contact support if the issue persists.
ERROR Undefined:This may be a result of job submission failure, job abort or perhaps a server-side error. If this persists please contact the developer for details.