I have no idea. According to the logs, the exclude list file just wasn't there anymore when filebot was called.
I recommend setting an absolute path to an exclude list file somewhere that you know for sure isn't being touched by filebot or any other tool you may have forgotten about.
I'd start by checking if the exclude list exists before/after running filebot. If the file disappears before/after filebot is called, then you know that another tool is the culprit.
EDIT:
This log indicates that the exclude list file was removed while filebot was running:
Code: Select all
Use excludes: D:\Done\SERIJE\amc.txt
Ignore hidden: D:\Done\BTN\desktop.ini
D:\Done\SERIJE\amc.txt
java.nio.file.NoSuchFileException: D:\Done\SERIJE\amc.txt
at net.filebot.util.FileSet.append(FileSet.java:171)
at Script1.run(Script1.groovy:298)
at net.filebot.cli.ScriptShell.evaluate(ScriptShell.java:64)
at net.filebot.cli.ScriptShell.runScript(ScriptShell.java:74)
at net.filebot.cli.ArgumentProcessor.runScript(ArgumentProcessor.java:113)
at net.filebot.cli.ArgumentProcessor.run(ArgumentProcessor.java:30)
at net.filebot.Main.main(Main.java:120)
The "Use excludes" will create a new file and fail if it can't. But then just a bit later it fails because the file that should exist doesn't.
There's something running on your system that's periodically deleting the exclude list file.