Hi
I am wondering about what limitations exists for the file archive action node, other than the usage of it (We are currently paying for increased use of this action node). A couple of Appfarm updates ago you said you increased the timeout, but what is the current timeout and is it possible to increase even more? Our users are pretty easily able to hit this timeout.
Could you also give an indication on any restrictions regarding file types and files size (both for the final zip, but also - if any - for the individual files in the zip)?
And finally, it would be extremely helpful if there was a way of displaying the “zip progress” so that we could add a loading progress bar instead of a static loader, similar to how “Upload progress” works on file data sources.
Following up on my own thread:
I guess i figured out that the timeout is 300.000ms (or 5 minutes). Can this be increased? Facing some inconsistencies, where i can zip 19 files thats 53mb each (ish 1GB in total) but it reaches timeout for 44 files thats 8,5mb each (ish 340mb in total), which to me is a bit confusing. File name sanitation is done before using the file archive node, and the path is limited to only the parent folder to remove any large calculations when archiving. Any ideas of how we can make this work more reliable?
Hello,
Regarding the timeout limit, I am looking into whether or not it can be exceeded.
I am not familiar with restrictions on individual files going into the file archive. I can give you a more specific answer on this when I hear back from the devs team.
I will register a feature request for a progress indicator when using the file archive action node. This would indeed be very helpful for end users when creating zip files.
Thank you so much for the feedback and for giving us some examples of inconsistencies, I will get back to you when I have more information 