FileWatch blocks with non-existent directory

Current Behavior:

In the workflow associated with a file order source, if the provided directory path does not exist, the agent will continuously attempt to register the directory. However, these attempts will fail each time, as the directory is absent. A new directory can only be registered once the registration process for the previous directory has been successfully completed. Since the directory does not exist, the process cannot proceed.

Steps to Reproduce:

1. Create a workflow (w1) and attach a file order source (f1).
2. Set the directory path of the file order source to C:\Users\test.
3. Execute the file order source.
4. Modify the directory path of the file order source to a non-existent path, such as C:\Users\test_ (by adding an underscore at the end).
5. The order will fail to run for the modified, non-existent path.
6. Provide the correct directory path again in the file order source.
7. The system will still use the modified path (C:\Users\test_) and will not execute the order, even though the correct path was provided.

Desired Behavior:

Upon a configuration update, if the specified directory does not exist, the registration process should automatically cancel. The system should then allow for the registration of a new, valid directory, ensuring the process can proceed with the updated configuration.

Workaround: Create a directory with the incorrect path you provided (which does not exist) in the file order source so that the directory can be registered. Once registered, you can then rename the directory with the correct path and name, and it will work as expected.