scraping stops working after a bit if prowlarr is active

[ratchettest]

Issue Description

After updating riven to latest 18/19 backend and 17 frontend, scraping fails after some amount of time. Time to failure ranges from 10 minutes - 24 hours after a full rebuild if prowlarr integration is enabled. There was a note in the discord that said "dont use prowlarr for indexers that are already supported by Riven" which led us to turn off prowlarr to test again.

Thread ID 1305578488404770866 in Riven Support Channel

Docker Image Type

riven:latest 18.0 & 19.0 with riven-frontend:latest 17.0

OS Version and Last Update

Various

Error Logs and Timestamps

no errors in the logs - it just goes silent after it sees the request and ends with "Executor for scraping found". Logs from multiple users can be found in the discord thread ID.

24-11-18 09:33:23 | 🐞 DEBUG | event_manager.add_event_to_running - Added Item ID episode_12336925 to running events.
24-11-18 09:33:23 | 🐞 DEBUG | event_manager.remove_event_from_running - Removed Item ID episode_12336925 from running events.
24-11-18 09:33:23 | 🐞 DEBUG | event_manager.add_event_to_running - Added Item ID episode_12336925 to running events.
24-11-18 09:33:23 | 🐞 DEBUG | event_manager.submit_job - Submitting service Scraping to be executed with Item ID episode_12336925
24-11-18 09:33:23 | 🐞 DEBUG | event_manager._find_or_create_executor - Executor for Scraping found.
24-11-18 09:33:23 | 🐞 DEBUG | event_manager.add_event_to_running - Added Item ID episode_12338228 to running events.
24-11-18 09:33:23 | 🐞 DEBUG | event_manager.remove_event_from_running - Removed Item ID episode_12338228 from running events.
24-11-18 09:33:23 | 🐞 DEBUG | event_manager.add_event_to_running - Added Item ID episode_12338228 to running events.
24-11-18 09:33:23 | 🐞 DEBUG | event_manager.submit_job - Submitting service Scraping to be executed with Item ID episode_12338228
24-11-18 09:33:23 | 🐞 DEBUG | event_manager._find_or_create_executor - Executor for Scraping found.