Managing the concurrency issue between KNIME and a batch process during CSV file generation

Description: In my KNIME workflow, a CSV file is generated and deposited into a specific directory (Directory X). An external batch process (FEX process), which runs every 5 minutes, transfers this file to another directory. The issue arises when the CSV file is large: KNIME takes time to complete the generation. If the batch process runs while the file is still being created, it transfers it partially, leading to an incomplete and unusable file.

I have tested a solution that involves writing the file to a temporary directory and then moving it to Directory X once the generation is complete. However, KNIME takes nearly the same amount of time to perform this move—around 50 seconds—which does not fully resolve the issue.

Question: Is there a native or optimized solution in KNIME to address this problem? For instance, a way to delay the visibility of the file in the target directory until it is completely generated, or another strategy to avoid this conflict.