ERROR:0 - Issue with Jobs on the Server

[Ali Kalantari]

Dear FUMA team,

I recently submitted three jobs (Job IDs: 449350, 449351, 449352) to the server. Unfortunately, all three jobs encountered the same ERROR:0. The parameters and input files for these jobs closely resemble those used in similar jobs last year before the server update. I would greatly appreciate your assistance in resolving this error.

Thank you,

Ali

[Anastasios Mitsigkolas]

Hi there,

ERROR:0 means that the input file has not been uploaded to the server and it has nothing to do with the parameters or the type of the input file. Some people have reported this error again but unfortunately, I haven't been able to reproduce it. My suggestions are the following:

1. Try using a different browser and/or hard refresh the page. (Ctrl + shift + r)
   
2. Try using VPN.
3. Make sure that you don't move away from the window while uploading. (sometimes, takes a lot of time depending on the size of the file and internet connection speed.
4. Try a personal computer from a home network. (Sometimes networks in working environments are very strict)

Please let me know if it works.

Kind regards,
Tasos

[Asma Nouira]

Dear all,

I am encountering the same ERROR:0 with these JobIDs: 449533, 449556, 449559, 449561.
 I have tried the options suggested by Anastasios Mitsigkolas, but the issue persists.
I will keep an eye on this conversation for any potential solutions.

Thank you.

Kind regards, Asma

[Ali Kalantari]

Hi Tasos,

Thank you for your prompt response. I followed your suggestions and tried uploading the file again from a different network on campus. Additionally, I compressed the input file to .tsv.gz, which successfully resolved the ERROR:0 issue for job ID 449572.

However, I encountered a new error this time (ERROR:005), even though there are SNPs below the 5e-8 p_value threshold. The parameters and input files I used closely resemble those from previous jobs. Upon reviewing the parameters on the new job page, I noticed differences in the first section (1. Upload input files):

1. The option “Input is build GRCh38” cannot be checked, regardless of defining the effect and non-effect alleles.
2. “Identify additional independent lead SNP” is selected and cannot be unchecked.

When attempting to reproduce the same error, did you upload a GWAS summary statistics file that was built on GRCh37 or GRCh38? Please refer to the attached screenshots.

Thank you once again for your support.

Kind regards,

Ali

[Ali Kalantari]

Hi Tasos,

I just wanted to add that I encountered an Invalid JSON response warning while trying to add parameters for another job on the FUMA server. Specifically, I received the following warning:

                 DataTables warning: table id=ciTable - Invalid JSON response

Thank you!

Best regards,

Ali