Hi @giorgos93,
Thank you for your question. The scheduled tasks you mentioned (e.g., rsssl_every_five_minutes_hook, rsssl_every_three_hours_hook, rsssl_every_day_hook) are internal cron hooks used by the plugin to handle various background processes.
This includes actions such as fetching the latest plugin & theme vulnerability data daily, performing scheduled cleanups, checking the SSL certificate status and such. Each of these intervals is chosen based on how often that particular task needs to run.
We don’t recommend removing or changing the intervals manually, as the plugin relies on these scheduled tasks. Changing them manually could affect plugin functionality (or lead to outdated data e.g., in the case of the vulnerability scanner).
Kind regards, Jarno
Thread Starter
George
(@giorgos93)
Hi, @jarnovos ! Okay, I’ll leave the cron tasks, as they are.
However, I can’t run rsssl_every_five_minutes_hook every 5 minutes, because my CRON is set through server (hosting), and it triggers once an hour.
Is it okay, if rsssl_every_five_minutes_hook will trigger once an hour, instead of every 5 minutes?
Hi @giorgos93,
I see, that makes sense. Running the rsssl_every_five_minutes_hook once an hour (instead of every five minutes as the name suggests) should generally be okay for most sites.
With an hourly trigger, the actions that this depends on would just be delayed slightly. If an action (e.g., some clean-up process) is queued, this would make it take longer before it actually starts running; but it won’t break any core functionality of the plugin either.
Kind regards, Jarno
