Support Forum

is there a way to make them persistent again?

EDIT: found it, sorry

("queue_complete_pers" must be true)

It's working again on 3.5.1RC1

with 3.5.0 i can‘t even set a custom script on the main-webpage „when done“ same behavior as described above: when i select a custom script it jumps back to the previous selected one. Maybe it‘s a safari issue, as i updated to 15.3 recently. macOS Catalina latest security update. It works on mobile ...

It happens with Firefox too. I found out that i can switch between the other scripts, but NOT back to "nothing". So i simply made script "nothing.sh" as a workaround which does - nothing ;) I didn't see anything special when i did open the console and inspected the element regard...

Yes, i m using Glitter Skin.

I tried it with 3.3.0RC1 but it's still not possible to revert back to "do nothing" once a script is set for a certain job.

Setting a script for "on queue finish" works. I prefer job-based scripts, though.

I often use the option to run a script when a certain job is finished (e.g. last one in the queue). Since at least sabNZB 3.2.0 you can't revert to "do nothing" instead of the chosen script. Reproducable all the time on macOS 10.15.7

... but: it hadn't "#!/bin/bash" in the first line. The script is executed fine now from sabnzbd also.

Yes, it has. It is executable from Terminal just fine also.

I put some echo output to be written in a text file. The script works when called from terminal and logs to the text file, but not when called from sabnzb. The script isn't executed at all. I can get the system to sleep if i ssh into it and execute "pmset sleepnow" mybe you can add this co...

I put some debug output in the script. Problem is: the script does NOT run on postprocess-finish, even though the log says it did. Thats why the machine won't got to sleep mode. 2017-01-20 16:21:32,200::INFO::[postproc:815] Queue has finished, launching: <function run_script at 0x55cc530> (sleep-now...

Ah, OK. Thanks.

But shouldn't the stay-awake-module stop and allow the sleep script to launch after the queue has finished?

Is it possible to disable the stay-awake-module somewhere in the settings?

Do have a logfile entry?

I have the same issue and posted a bug report.

I'm on macOS Sierra. I made a rock-solid sleep script for commandline. It works perfect in every condition, but not with sabnzb. It isn't spwaned correctly, see here: <USERNAME> should be mine (ds) 2017-01-15 16:00:06,418::INFO::[postproc:85] Saving postproc queue 2017-01-15 16:00:06,419::INFO::[__i...

I guess the bug lies here. I made a rock-solid sleep script for commandline. It works perfect in every condition, but not with sabnzb. It isn't spwaned correctly, see here: USERNAME should be mine (ds) 2017-01-15 16:00:06,418::INFO::[postproc:85] Saving postproc queue 2017-01-15 16:00:06,419::INFO::...