This app checks whether a file exists at a specified path, which can be built dynamically using variables. Depending on the result, jobs are routed to the success connection or, if the check fails, to the warning or error connection, so your flow can react before further processing takes place.
With the "Invert logic" option, the check can be reversed: the job succeeds when the file does not exist. This is useful for detecting duplicates, for example to verify that an order or customer file has not been created yet.
The "Job handling strategy" option determines how a failed check is handled. The job can become a problem job, be routed to the red error connection, or be routed to the yellow warning connection when a missing file is an expected rather than a faulty situation. The warning route is particularly useful when a file is optional, so that its absence does not clutter the Messages pane with errors.
Typical use cases include waiting for required input files, validating dynamically constructed paths, and preventing jobs from overwriting existing data.
