Despite the implemented delay, however, the behavior described above happens again in some cases. Maybe the delay is too short Here i have now set the value of n to 3 (for 2 seconds of dalay), that seems to be a save solution.

If the ZIP file of a trunk was faulty for any reason (e.g. problems during download), this wasn't handled by the batch. Now this kind of error is also regarded with an error message (see batch code V1.1.0 in first post).