New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postprocessing frequency ignored #7895
Comments
Additional information: Looking at the last run time and comparing that to the current time + time until next run, it seems the next run is exactly 24h 10m after the previous run, instead of just 10m. |
Please try #7898 |
Please update to the new release: https://github.com/pymedusa/Medusa/releases |
Thanks, I'll let you know how it goes. Interestingly, after a manual postprocess last night, it ran every 10 minutes for 2 hours and then stopped. No files were processed during this period. I did not check the 'next run' before applying the latest updates, so I don't know what it did after that 2 hour time frame. |
All good. Running every 10 minutes, as required. |
I recently switched on automatic postprocessing. It doesn't seem to be processing my files in a timely manner.
When I look at the system status page, I notice that while the auto-postprocessing frequency is set to 10 minutes (as per the settings page and unchanged from the default, I believe), the time until next run is hours away.
How can a 10 minute interval lead to a time between execution of many hours?
Manual postprocessing is working correctly, including the execution of my custom script.
OS: FreeNAS 11.2-U8; iocage jail
Branch: master
Commit: where do I find this?
Python version: 3.7.6
Database version: Where do I find this?
The text was updated successfully, but these errors were encountered: