We have several jobs that kick off programs when certain data files show up in a network drive. I set up conditions to monitor this drive with a different mask for each task:

File Condition, True if file exists, on match any or all then continue. Or error or match none then exit.
Path: \\servername\sharename\XYZ_010*.*

*Note: Makes no difference to the operation if the fully qualified path is used or not.

The conditions worked just fine and the jobs would not run unless the file(s) were there. When I restarted the machine, now the jobs never run, even if the files ARE there. I've tried restarting again, and messing with the conditions. Nothing has changed except the restart. Service and tray client are running as the same user as before, same drives are mapped on the foreground session. The only way to get the jobs to run is to disable the condition entirely and I really can't do that. I need the conditions in place.

Seems like it can no longer access that drive, could that be the case? That would sound natural if the Job just exits.

---

Nevermind, I ended up fixing my own problem. It was an idiotic oversight on my part. I have about 5 tasks per job to be run in order. I had the On Match None set as Exit and not Next. So it would just exit the entire job if the first task was not to run and never evaluate the remaining conditions. Switching them to Next fixes the problem. Sorry about this.

No problem

---