The behavior you're seeing is expected in Mendix as mendix does not support this and a microflow can only send one file download response back to the browser. If you call Download File inside a loop, only the last file processed File C in your example in your case will be downloaded.
For example:
Loop 1 → Download File A
Loop 2 → Download File B
Loop 3 → Download File C
The browser ultimately receives only the final response, so only File C is downloaded.
The recommended approach is to -
If you're getting a "Contact your administrator" error when downloading the ZIP, I would check:
Since you've tried both a custom Java action and the ZipHandling module and are seeing the same behavior, the issue is likely related to the generated ZIP FileDocument or the download step itself rather than the ZIP implementation.
Hi Harsh,
Punam is right,
But for workaround it'll be better to move the download file logic to the client ( nanoflow )
and for zipping the file you can use use this code.
But this will require you to download the @zip.js from npm in your node modules.
Your package json should look like this
{
"dependencies": {
"@zip.js/zip.js": "^2.6.15",
}
}