Post Process Not enabling even though sliders enabled in post processing settings (manual work around via config.ini) If you set this feature and review the server Status the post processing enable flag is set to FALSE.
Please note this is on a fresh install of Medusa and think is related tot eh change from the tickbox to the slider and so the value isnt updating the config.ini
The manual fix for the auto processing for X time is to manually edit the confi.ini and update process_automatically to a value of 0
To Reproduce
Steps to reproduce the behavior:
Expected behavior
These two value should enable Medusa to auto scan the download folder for changes (which it does not) and also auto process the folder every X minuties.
Medusa (please complete the following information):
Hey! The False doesn't mean it's not working, it just means it _currently_ isn't running. Maybe you have set a lower post-processing frequency? You will need to wait 10 min for it to start in that case, see https://github.com/pymedusa/Medusa/issues/5346
Hey there,
I had this set to 10 mins which should be fine... its just that after enabling the process was marked as disabled even though all my values were set as to run this process. the only way i could get it to run with the 10 min intival was to manually adjust the config.ini value and then the timed process would run.
Even doing this its not running on a change to the folder but i can live with an intival scan.
I just wanted to raise this for awareness as i litterally installed Medusa yesterday as i only found out about this fork yesterday so was just trying to work out why it wasnt running as it should as i never had this issue with Sickrage which i was using prior to this.
I had this aswell if you check server status it will say post process enable = False. After a restart it will be on True
I was having a similar issue. As @Tearow said once I restarted the server it connected the post-processor. Not sure why I didn't think of this before.
Most helpful comment
I was having a similar issue. As @Tearow said once I restarted the server it connected the post-processor. Not sure why I didn't think of this before.