If you have a dependent operation that is not dependent on the current job producing a file, it would make sense to have the action set to Continue.
The Stop and Error options won't prevent the blank file from being generated but will stop it from being sent to the designated target. It will also prevent any dependent operation from being activated (or will have the error dependent operations fire instead).
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 909-900-9179
------------------------------
Original Message:
Sent: 02-22-2022 11:37
From: Vijay Zarapala
Subject: Empty File Action use-cases
Hi EW community, this question is to understand the benefit of setting "empty file action" as "CONTINUE" for scheduled exports. Due to this, a blank file is generated even when there is no content to be exported. To optimize resources and prevent generation of blank files, we are planning to change it to STOP or ERROR. I checked the admin manuals 10x and would like to know if there are any benefits of keeping this Empty File Action setting as CONTINUE instead of STOP? We are in EW 10x now.
------------------------------
Vijay Zarapala | Senior PIM MDM Developer
HD Supply | Home Depot
------------------------------