Solved
Folder Monitor profile event malfunction
Hello Joao, I would like to report a bug that persists in this version I think. But not really sure if it's an error or if Tasker should work like this way actually.
+ > Profile (event) > File > (all of them)
The "bug" is that if there is more than one profile monitoring the same directory (e.g. /Download), the following will happen:
-
If both profiles are enabled, only one of them will get fired (the last created one most of the times).
-
If one of the profiles is disabled, the other won't get fired. Here doesn't matter when each one was created, no one runs its task.
So, the solution to the above is to delete one of them, so you can get the profile to work again.
I have tried with the following workarounds if something helped, but nothing:
-
Play with the launched task priority of both profiles.
-
Toggle 'Enforce Task Order', but I don't think it makes sense.
If finally these kind of profiles can't work together (same dir/file monitored), something like allowing Tasker to make the profile that is active to work, taking into account that the other possible profiles are already disabled. Would be a good "fix" to apply. This will prevent us from having to rename the dir (like: /DownloadX) temporarily, or delete them if we have various of them somewhere.
So please, if you can take it a look I and we all will thanks you it 😉🤝.
