SAB Queue incorrect or is it?

[pguillot69]

Just notice it lately.
The Queue used to be loaded as LILO and not its working as FILO.

For the programmers in the group the Queue is acting like a stack and all NZBs are getting pushed onto the stack. They pop off the same way. I thought the queue was supposed to grow at the bottom.

Is there a setting that I missed that changed the way the QUEUE is handled?

Would have loved to have the system work the NZB first as a checker to see if the NZB is valid, then place it in a processing queue.

This would help SONARR in its processing to remove the garbage NZB's and process the the valid ones. As it is, I have to limit the number of NZB's pushed to SAB to keep the queue from overloading.

Would be great to have a limiter on the Queue also. Say a setting that would be set that would allow Max of 50 in the queue. SAB would send a queue full to any third party program. Sonarr checks to see if a downloader is present or available so that would be an option too.

Thanks for a great program.

[sander]

The SAB queue is FIFO, but you can override stuff with the priority per item. So check priority.

Pre-check can be done with pre-processing script.

Limit on queue? Sonarr can check the queue length, and ETA, and back off if it wants to.

[safihre]

Or you have enabled automatic queue sorting in Config Switches.