Millisecond Forums

I've run an experiment (ID 76490) with ~1000 participants, each of which produces ~20 files. When I try to export this data after a new wave of testing (~200 participants in a single day), invariably many files are missing in the exported zip file, even though their existence can be verified thru the file browser on the inquisit website. What causes this and what can be done about it? 

+x

 

Sercan - 3/10/2026

I've run an experiment (ID 76490) with ~1000 participants, each of which produces ~20 files. When I try to export this data after a new wave of testing (~200 participants in a single day), invariably many files are missing in the exported zip file, even though their existence can be verified thru the file browser on the inquisit website. What causes this and what can be done about it? 

What's the account name or experiment URL?

+x

 

Dave - 3/10/2026

+x

 

Sercan - 3/10/2026

I've run an experiment (ID 76490) with ~1000 participants, each of which produces ~20 files. When I try to export this data after a new wave of testing (~200 participants in a single day), invariably many files are missing in the exported zip file, even though their existence can be verified thru the file browser on the inquisit website. What causes this and what can be done about it? 

What's the account name or experiment URL?

The URL is mili2nd.eu/kwkc

+x

 

Sercan - 3/10/2026

+x

 

Dave - 3/10/2026

+x

 

Sercan - 3/10/2026

I've run an experiment (ID 76490) with ~1000 participants, each of which produces ~20 files. When I try to export this data after a new wave of testing (~200 participants in a single day), invariably many files are missing in the exported zip file, even though their existence can be verified thru the file browser on the inquisit website. What causes this and what can be done about it? 

What's the account name or experiment URL?

The URL is mili2nd.eu/kwkc

Thanks. It's an API timeout issue -- all the iterating through roughly 14k files in dozens of subfolders ultimately takes so long that it hits the maximum process time allowed by the file access API and then stops, an incomplete archive being the result.

The best workaround for now is to navigate into the delayaat folder, select all subfolders, then select download as ZIP. This will give you 13 ZIPs, one per subfolder. Nothing there will hit the timeout, since these are generated in separate processes. I've tested and verified that they are complete, i.e. contain all 13904 data files currently available.

+x

 

Dave - 3/10/2026

+x

 

Sercan - 3/10/2026

+x

 

Dave - 3/10/2026

+x

 

Sercan - 3/10/2026

I've run an experiment (ID 76490) with ~1000 participants, each of which produces ~20 files. When I try to export this data after a new wave of testing (~200 participants in a single day), invariably many files are missing in the exported zip file, even though their existence can be verified thru the file browser on the inquisit website. What causes this and what can be done about it? 

What's the account name or experiment URL?

The URL is mili2nd.eu/kwkc

Thanks. It's an API timeout issue -- all the iterating through roughly 14k files in dozens of subfolders ultimately takes so long that it hits the maximum process time allowed by the file access API and then stops, an incomplete archive being the result.

The best workaround for now is to navigate into the delayaat folder, select all subfolders, then select download as ZIP. This will give you 13 ZIPs, one per subfolder. Nothing there will hit the timeout, since these are generated in separate processes. I've tested and verified that they are complete, i.e. contain all 13904 data files currently available.

Thanks for looking into it Dave, downloading every subfolder separately did the trick.