Cron running/rescheudled on every page load?

  • Resolved eclev91

    (@eclev91)


    1 month, 3 weeks ago

    Hey all, I could be wrong here, but I’m pretty sure this line here is processing your cron queue on every single page load.

    Now it’s possible that there isn’t always anything meaningful hooked into that cron process on page loads, but if nothing else, Site Health gets worried about this because it results in a perpetually overdue cron job.

    And by putting everything into your own abstracted queue logic on a single hook, largely circumventing the WP queue system, it’s hard to use traditional WP Cron tools to debug what this plugin is doing. I don’t love it.

    I understand the concern about zombie processes, but that’s what the deactivation hook is for.

    Just my two ?? I suppose

Viewing 1 replies (of 1 total)
  • Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello @eclev91

    We discussed this internally with our developers, and here’s what they’ve shared so far:

    From what we’ve seen, this setup works as expected, and there don’t seem to be any strong reasons to avoid it aside from the warning on the Site Health page. If there’s a need to modify the list of runners, it can be done via the following service: Zettle POS Integration. However, I’m not sure if we’ve had examples of extending the modules.

    As for wp_schedule_single_event, all we are doing there is to re-register a?single?event on every page load (as opposed to registering a recurring event once, persistently). The actual processing of events is still handled by WP normally.

    We’re not sure if Site Health existed when this was put in place. We understand that it looks weird to have an overdue job sitting there at all times (even though a 1-second delay really should not raise concerns given the nature of vanilla WP cron).

    It could only make sense to replace this with a recurring job + deactivation hook. Or somehow silence that Site-Health-Item because I don’t think we’re doing something wrong – and a cron schedule has other implications.

    If there will be some updates regarding this topic from developers I’ll share more information here, and we’ll let you know.

    Kind Regards,

    Krystian

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.