inactive 'History' tab text always updates after PP, but not always with correct text, when UI refresh is 1 second
Posted: March 26th, 2025, 6:26 pm
Hi guys, I've been seeing this for a while and thought I should do some investigation today so I can report it. 
Post-processing completes, but the 'History' tab text doesn't always update correctly. Sometimes it will show "1" (which I think is correct), sometimes it shows "1 2" (incorrect). This happens regardless of the exit status of post-processing. The 'History' tab text will stay like this until I refresh/reload the web page (but I assume if another job is processed, it will update itself). After refresh, the ‘History’ tab text is “1”.
This occurs at-random (but only when the tab text should be updated).
With 2 different browsers open (Firefox and Chromium), it can occur in one browser window and not the other, and appears to be random as-to which browser it is displayed incorrectly. Sometimes it works fine in both, sometimes it fails in both.
Thoughts?
- SABnzbd 4.4.0 from source on Debian 12.10
- Accessing the UI via Firefox 136.0.3 (although, this bug has been around for multiple Debian, Firefox and SABnzbd versions). Also checked this in Chromium 134.0.6998.35
- UI access is via HTTP-only on a separate LAN PC.
- UI theme is glitter-night.
- UI is using tabbed layout.
- Python 3.11.2
- 1GbE LAN.
- SABnzbd web interface refresh is set to 1 second (note: bug does not occur when this is set to 2 seconds).
Post-processing completes, but the 'History' tab text doesn't always update correctly. Sometimes it will show "1" (which I think is correct), sometimes it shows "1 2" (incorrect). This happens regardless of the exit status of post-processing. The 'History' tab text will stay like this until I refresh/reload the web page (but I assume if another job is processed, it will update itself). After refresh, the ‘History’ tab text is “1”.
This occurs at-random (but only when the tab text should be updated).
With 2 different browsers open (Firefox and Chromium), it can occur in one browser window and not the other, and appears to be random as-to which browser it is displayed incorrectly. Sometimes it works fine in both, sometimes it fails in both.
- If I switch the SABnzbd web interface refresh to 2 seconds, it appears to be 100% reliable. 'History' tab text updates correctly to "1" on next item processing if the history has been cleared.
- If I have the 'History' tab active when post-processing is complete, it also appears to be 100% reliable.
Thoughts?