Dale Wassum (Customer) asked a question.

September 22, 2026 at 5:52 PM
Does anyone have a good solution to detect and alert admins when the MOVEit Automation file notifications / filesystem notifier is not functioning properly?

We have a recurring issue where the file notification service stops functioning randomly, after which no tasks are triggered automatically on file arrival. When filesystem notifications are working properly, the "Started by" column in the Task Run report log contains the value "(filesystem notifier)". When this stops working, the only solution we have found is to restart the MOVEit Automation service, or in some cases reboot the MOVEit Automation server.

 

Most of our tasks which use Windows file notifications at the (UNC) source host will typically have recurring schedules to "Poll for files even though file notifications are also enabled," but sometimes our users notice when files are not being transferred promptly in the usual manner. I would like to create a solution which can proactively notify admins when this issue starts occurring and new files are not being detected by the filesystem notifier.

 

It would also be helpful to know if other MOVEit Automation users/admins have encountered this recurring issue. In our environment, it seems to have started happening more frequently over the past year or so. We are currently running MOVEit Automation 2026.0 and plan to update to the latest service pack soon. Any help you can offer is greatly appreciated.

  • 1 answer
  • 37 views

  • Vanshdeep Khurana (Progress Software)

    Hi Dale,

     

    MOVEit Automation file notifications for Windows/UNC sources rely on the Windows ReadDirectoryChangesW mechanism. To add, the Windows filesystem notifications are not 100% reliable and can occasionally miss notifications or stop working for particular folders.

    For this reason, we recommend keeping “Poll for files even though file notifications are also enabled” enabled on the task schedule. This provides a fallback so files are still detected if the filesystem watcher misses an event. For the recurring condition you are seeing, I would suggest:

    1. Upgrade to the latest applicable 2026 service pack as planned.
    2. Continue using periodic polling as the fallback for critical tasks.
    3. If the notifier continues to stop functioning after the upgrade, open a Progress Support case so logs can be collected while the issue is occurring and the underlying notifier failure investigated.
    4. For proactive monitoring, monitoring the absence of (filesystem notifier) executions could be useful as a custom operational check, but there is no built-in MOVEit Automation alert specifically for detecting a stalled Windows filesystem watcher.

    Your existing polling configuration is therefore the correct recommended safeguard.

     

    Let us know if you have any follow-up questions. Thanks

     

     

     

    Regards

    MOVEit Support