I have a job that is triggered based on a remote file. There are 2 that are being downloaded. The job triggers, downloads both files and runs the job like it should. Once it reaches the last task in the job, it triggers again. This then causes a failure as there are no files to download or process.
The issue is, I am doing the same thing on another job and it is not triggering again at the end.
Why would one be so drastically different than the other?
Job that re-triggers after last task:
*the set job variable task is looping through the files listed in the task before it as we only want to process one file at a time.
*Also, the loop does not change the outcome when it comes to the trigger going off a second time upon completion of the last task in the job. I have tried with and without the loop.
*The wait was added as a way to make sure files were fully archived before continuing on. This did not fix the issue of re-triggering.
Job that does not re-trigger: