ClassyFire Batch Stops Processing InChIKeys Mid-Query

[Former user]

I fed the batch search a small subset of InChIKeys that weren't originally found when using the classyfire.wishartlab.com/entities/<InChIKey> API call, but the batch search stops functioning and hangs after processing the first InChIKey. What can be done to proceed with this?

The InChIKeys used are below: DILIRPYTYVKBTJ-UHFFFAOYNA-N LHJLPUYZALAANW-UHFFFAOYNA-N VZIGYDSNXDJOKN-UHFFFAOYNA-N WQAZXAXYEBZZFT-UHFFFAOYNA-N QONJHDDRLAVBMT-QWOVJGMINA-N ZVBBYXDSHXDOCM-HCKMINDGNA-N BWNSTBOTBDUYFD-HCKMINDGNA-N WBNSIQODMOYOLW-YENFCIRVNA-N VSJJRSNKEPVLNB-WYUMXYHSNA-N

[Brady Anderson]

The bug occurs whenever the status is “Completed” and nothing is queries for the kingdom, superclass, etc. It also seems to occur for certain InChIKey’s when searched again even if compound class information has been able to be gained using this tool before. The software is unusable until this bug is fixed, which is a shame since this is the best option out there.

[Shaw]

I met the same problem: the status is 'completed', but no compound classifying result. Does that show, the structure exists in the ClassyFire database, but no classify information? Actually, the frozen really disturbs the batch search.