Hazel rules do not run automatically for a Synology folder
Posted: Tue Mar 31, 2026 11:23 am**Hazel version:** 6.1.2
**macOS version:** Tahoe 26.3.1 (a) (25D771280a) (Apple Silicon M2)
**Summary:**
Hazel rules do not run automatically for a folder located in ~/Library/CloudStorage/SynologyDrive-SynologyDrive/. The rules match correctly in the preview and run successfully when triggered manually via "Run rules now", but are never triggered automatically by file system events.
**Folder being monitored:**
/Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/action - MyDrp
**Steps to reproduce:**
1. Add a folder inside SynologyDrive (under ~/Library/CloudStorage) to Hazel
2. Create a rule with conditions on Color Label, file Name, Kind, and Name contains
3. Add a file matching the rule to the folder
4. Observe that the rule never triggers automatically
5. Manually trigger via "Run rules now" — rule runs correctly
**Expected behavior:**
Hazel should detect file system events and trigger rules automatically, as it does for local folders.
**Actual behavior:**
The log repeatedly shows:
Attempted to run worker on undeployed folder: /Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/action - MyDrp
This occurs every time a file system event is detected. The worker is never successfully deployed for automatic processing. When "Run rules now" is used, the worker deploys correctly and rules execute as expected.
**Additional observations:**
- The issue appeared recently — this setup has worked reliably for years without configuration changes
- Restarting Hazel does not permanently resolve the issue; "undeployed folder" errors resume after the next file event
- Rules preview correctly in the Hazel UI and show "Rule matches"
- Manual "Run rules now" always works
- The folder option is set to "Force file to be downloaded" (iCloud/cloud storage setting)
- Other folders (e.g. local Downloads) deploy and process correctly
**Relevant log excerpt:**
Note: The "undeployed" error at 17:09:20 occurs immediately after a successful forced run, showing the worker is not staying deployed between events.
**macOS version:** Tahoe 26.3.1 (a) (25D771280a) (Apple Silicon M2)
**Summary:**
Hazel rules do not run automatically for a folder located in ~/Library/CloudStorage/SynologyDrive-SynologyDrive/. The rules match correctly in the preview and run successfully when triggered manually via "Run rules now", but are never triggered automatically by file system events.
**Folder being monitored:**
/Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/action - MyDrp
**Steps to reproduce:**
1. Add a folder inside SynologyDrive (under ~/Library/CloudStorage) to Hazel
2. Create a rule with conditions on Color Label, file Name, Kind, and Name contains
3. Add a file matching the rule to the folder
4. Observe that the rule never triggers automatically
5. Manually trigger via "Run rules now" — rule runs correctly
**Expected behavior:**
Hazel should detect file system events and trigger rules automatically, as it does for local folders.
**Actual behavior:**
The log repeatedly shows:
Attempted to run worker on undeployed folder: /Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/action - MyDrp
This occurs every time a file system event is detected. The worker is never successfully deployed for automatic processing. When "Run rules now" is used, the worker deploys correctly and rules execute as expected.
**Additional observations:**
- The issue appeared recently — this setup has worked reliably for years without configuration changes
- Restarting Hazel does not permanently resolve the issue; "undeployed folder" errors resume after the next file event
- Rules preview correctly in the Hazel UI and show "Rule matches"
- Manual "Run rules now" always works
- The folder option is set to "Force file to be downloaded" (iCloud/cloud storage setting)
- Other folders (e.g. local Downloads) deploy and process correctly
**Relevant log excerpt:**
- Code: Select all
2026-03-31 16:59:38.717 86Z3GCJ4MF.com.noodlesoft.HazelHelper[800] Attempted to run worker on undeployed folder: /Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/action - MyDrp.
2026-03-31 16:59:38.974 86Z3GCJ4MF.com.noodlesoft.HazelHelper[800] Attempted to run worker on undeployed folder: /Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/action - MyDrp.
2026-03-31 17:03:16.112 86Z3GCJ4MF.com.noodlesoft.HazelHelper[800] Attempted to run worker on undeployed folder: /Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/action - MyDrp.
2026-03-31 17:09:05.146 hazelworker[10145] Processing folder action - MyDrp (forced)
2026-03-31 17:09:07.589 hazelworker[10145] 2026-03-25 - info kreditsafe kreditupplysning hygglo extrainfo micke.pdf: Rule If GREEN & info -> Archive matched.
2026-03-31 17:09:07.589 hazelworker[10145] [File Event] File moved: 2026-03-25 - info kreditsafe kreditupplysning hygglo extrainfo micke.pdf moved from folder /Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/action - MyDrp to folder /Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/arkivet.
2026-03-31 17:09:07.591 hazelworker[10145] [File Event] File moved into subfolder: /Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/arkivet/2026/info/2026-03-25 - info kreditsafe kreditupplysning hygglo extrainfo micke.pdf
2026-03-31 17:09:11.958 hazelworker[10145] Done processing folder action - MyDrp
2026-03-31 17:09:20.867 86Z3GCJ4MF.com.noodlesoft.HazelHelper[800] Attempted to run worker on undeployed folder: /Users/micke/Library/CloudStorage/SynologyDrive-SynologyDrive/action - MyDrp.
2026-03-31 17:13:37.711 hazelworker[10265] Processing folder action - MyDrp
2026-03-31 17:13:39.879 hazelworker[10265] Done processing folder action - MyDrp
Note: The "undeployed" error at 17:09:20 occurs immediately after a successful forced run, showing the worker is not staying deployed between events.