Hello again Rednoah. I've run into a new problem since updating Filebot with Snapd. I've been running a Filebot script using crontab for several months now with no issues. Everything was running perfectly fine until I installed Filebot with Snapd. (the Snapd install may be coincidental, but it stopped working right after)

My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.

Environment variables such as $PATH are different when run via cron. Run which filebot in console, have a look at the folder, and then make sure that that folder is in the $PATH(by adding it yourself) before calling filebot in your script.

My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.

Thanks for your help rednoah. Adding an extra $PATH to the beginning of the script fixed the problem.

Looks like the Snapd installed version of Filebot runs from a completely different folder that crontab doesn't recognise. In fact, I checked $PATH before I made any changes in the script and then added the new $PATH. I checked to make sure it was added and then ran the tests to see if it properly called Filebot. Here is an example of the script I used.