Directory Watch topic does not fire

So you are trying to see the output in notifications (using websocket). It may be that directory watcher is working but the notification service isn't (that can be all sorts of things, such as port blocking).

Do you have access to the Server that FME Server sits on? If so, you can go and have a look at the log file for publisher. Its in:

<FMEServerSystemShare>\\resources\\logs\\core\\current\\publishers

In there is a file called "dirwatch" and that records every time the directory watcher fire.

Based on what I'm seeing in the log I would say it's firing:

Thu-16-Jun-2016 08:42:53 AM INFORM main 801006 : Publication "Directory Watcher_Publication" configuration added. Path: \\\\sc58mcadp01\\$ecadcon\\mapsource\\DESIGNER1_DWG\\Central_Pacific\\Central_States\\DWG\\BELLEVILLE\\ADDRESSING\\Extension Addressing\\2015-7035 Cottages at Cathedral Square BV051R20 ADDRESSES.xls, Recursive: Yes, Topics: Thu-16-Jun-2016 08:42:53 AM INFORM main 801006 : Publication "Directory Watcher_Publication" configuration added. Path: \\\\sc58mcadp01\\$ecadcon\\mapsource\\DESIGNER1_DWG\\Central_Pacific\\Central_States\\DWG\\BELLEVILLE\\ADDRESSING\\Extension Addressing\\2015-7039 Access Point- Motel 6- 92722 BV120R7 ADDRESS.xls, Recursive: Yes, Topics: Thu-16-Jun-2016 08:42:53 AM INFORM main 801006 : Publication "Directory Watcher_Publication" configuration added. Path: \\\\sc58mcadp01\\$ecadcon\\mapsource\\DESIGNER1_DWG\\Central_Pacific\\Central_States\\DWG\\BELLEVILLE\\ADDRESSING\\Extension Addressing\\2015-7072 Sullivan Meadows BV060R15 ADDRESSES.xls, Recursive: Yes, Topics:

This appears to have been related to the NET service account and upon changing them back to Local System resolved that particular issue.

Thanka