Check File Raises an Error

Good time of the day.

Ran into an issue in Advanced ETL, where an error is raised on evaluating whether the file exists. This is the setup:



We check if a file with a specific file date exists. Process the file if it does. Alert via email otherwise.

When the file does not exist we correctly raise an alert and workflow continues on, but we also produce an error in execution.



This error gets bubbled up to the job scheduler and we end up reporting a job failure. This is not something that we want from this task. Is there a way for us not to produce a failure when the file is missing? We don't want an error to be raised, when it's normal for this process to be missing one, or both of the files.

Thank you!

Dmitriy

Nothing wrong with that.

Every action has two states success or failure

File exists = Success
File does not exist = Failure

I think the package execution is failing for a different reason.
Have you checked the package execution log?

Hi Mike,

This does appear to be the reason why it's failing. The screenshot is attached.



Thanks!

Dmitriy

Mike,

Yeah, maybe. I did not think about it from standpoint of overall design and architecture. Just seems odd. What is the use of an "IF" statement, if it doesn't let you have an alternate workflow?

Is there any other way to achieve the desired result without raising a failure?

Thanks!

Dmitriy

This does appear to be the reason why it's failing. The screenshot is attached.

Well thank you for posting the screenshots

Guess what? Somewhere before the lines we can see on the screen right now there is a line that tells which object is failing but we cannot see that line on the screenshot you posted.

Same issue with the original screenshot. The execution continues after line 8 till line 16. somewhere after line 16, it fails.
But we cannot see that line.

How do you expect us to help you?