Directory Watch in Automation does not watch

Hi ​@vxn43,

A few things could be going on here.

1. Where is the directory you are trying to watch? Is it local or somewhere on the network?
2. Is this an express installation? And are the Core, Web, and engine services running under a service account or Local System?
3. Could you expand on how you are running this process manually? What is your workflow that works? Is it working in just Form or Flow as well?

Dylan

Hello Dylan, 

1. Where is the directory you are trying to watch? Is it local or somewhere on the network? (It is on our network and the FME Flow server can communicate with the server where the directory is located, the directory is also shared.) ---- do I need to add the folder the Directory Watch is watching to Files - Connections - Resources?
2. Is this an express installation? And are the Core, Web, and engine services running under a service account or Local System? (This is an on-premises Fault Tolerant Installation, Engine1 and Engine2; all run under Local System)
3. Could you expand on how you are running this process manually? (For manual, I use Manual Trigger in the Automation) What is your workflow that works? Is it working in just Form or Flow as well? (The workflow works in FME Form no issues, the issue is that when i use Directory Watch in the Automation and new files are placed into the folder the Directory Watch does not trigger)

Is there another “Event to watch for” I need to add? currently I have Create, Modify, Delete.

Hi ​@vxn43, 

Specifically, does the service account running the FME Flow Core service have read/write permissions to the directory you are trying to watch? You shouldn’t need to add the folder as a resource connection in Flow, but it could be a good test to determine if FME Flow can connect to the folder.

I’d recommend checking your action_fmelogaction.log, fmeautomations.log and trigger_dirwatch.log for any errors or helpful messages. These can all be found at Resources > Logs > Automations.

Please see the following documentation below as well: 

Managing Resource Connections

Automations Resource or Network Watch Trigger

Dylan