Good day- I read a thread on the forums about the expected queue behavior when you run multiple instances of filebot with the --log-file parameters. I'm not sure if I am alone on this method, but I run my torrent client in a docker, so I execute filebot on the host, and I have no event-driven ...

Hello- I was looking at my logs and noticed this error message. Despite it, everything seems to be working fine. Any suggestions on what I need to change? Run script [fn:amc] at [Wed Jun 01 09:20:03 EDT 2022] Parameter: excludeList = /var/log/FileBot-excludeList.txt Parameter: seriesFormat = /mnt ...

Thank you, this works well now.

Darn, wish I could figure this out, I have a number of things linked to pushover. I'm running Filebot on my Synology, not sure if that matters with the functionality. Can you think of any dependency I would need? Is there a more verbose logging I can enable?

Hi-

Just upgraded to the latest RC2 and it's still sending a blank pushover message.

Best

I am also experiencing this issue, the pushover body is empty except a bullet with no text (regardless of the number of files processed). I've produced a example to show: Command: filebot -script fn:amc --output "/volume1/video" --log-file /volume1/homes/@LH-xxx/0/mike-1026/FileBot-log.txt --action ...