I will add another 'vote' to this has been happening for three weeks. My OMITB files have also been dumped into the unsorted pile.

Will try your commands when I get access to my server but clearly something's off if other people have been having the same issue.

Dealing with the whole DSM 6.2.4 update issues, node got deleted/uninstalled and I had to reinstall it. In the meanwhile it lost all config, license and tasks. Unfortunately what I had on my scheduler scripts were calls to node tasks as in: '/usr/local/filebot-node/task 1533066125345123' Not sure if...

Perfect, thanks! And apologies if I 'unwarrantedly poked' your new & fancy exit codes!

Should I do anything to update the AMC script or will filebot just download the most recent version in some days time/whenever it's ready?

Thank you once more!

rednoah wrote: ↑08 Apr 2019, 17:21 What's the command you're using in Scheduler? Are you using commands created by FileBot Node?

yep. See below. Only diference from usual is the 'send email when script terminates abnormally".
PS: thanks for the support!

I can, but I actually want to know when a legitimate problem happens, that's I had the 'email me on error' feature activated. As I said, I can write a wrapper script that treats exit code 100 like exit 0, and that would solve my problem. But unless I'm the only one running into this, I would say an ...

The exit code of 100 (NOOP) seems to be giving me a couple of issues. Specifically, I have the amc script running a couple of times a.day on a synology nas, through the system scheduler with the option to send me an email everytime an error occurs. Since 4.8.5, every time it runs without any new fil...

Hi folks. I've spent the last hours trying to get this to work and it's driving me mad. I wonder if you could assist me? I'm currently on a Mac with Mavericks, filebot v.4.5.6 form Homebrew Cask, Transmission 2.8.4. My problem appears to derive from some torrents coming within a folder and somehow t...