The difference in this situation is that has found that Hazel seems to trigger appropriately whereas the Folder Action does not. If you open the file, you’ll find the file path or paths of whatever triggered it. The file will be named "triggered_at_." where the suffix will be a date-time string ( yyyymmddhhmmss) that tells you exactly when the trigger fired. Every time this happens, you will find a file appears in your ~/Documents folder (you can change this to something else if you prefer). After saving, you can add files manually to your watched folder or sync files from your iPhone so they appear in the watched folder. Therefore, if you were to open the workflow in Automator for editing, you can deactivate all of its current actions (this is just to spare the hassle of deleting them and later having to recreate them-either way, they need to not be functionally affecting this diagnostic test), and insert the action I proposed at the top. In order to diagnose the problem with your workflow, you must first establish whether these iPhone files trigger the folder action at all, which isn’t something you can discern from your present workflow. You currently have a Folder Action set up to watch for file addition to your iCloud drive. This workflow, if implemented as a Folder Action, will report exactly when the action (rule) got triggered as well as the item or items responsible for triggering it. It was originally suggested by that you test whether your watched folder gets triggered and to determine what things are responsible for triggering it.
0 Comments
Leave a Reply. |