Interval Setting?

This is a good question!

It depends on when you saved the interval setting. Currently, the interval run time is completely separate from any other warm-up and is scheduled to run at the time you saved the interval setting. If you save the interval to 60 at 6:02, it will be scheduled to run at 7:02, 8:02 if no other warming is currently running (otherwise – skip; as the plugin can only run 1 warming at a time). So if the scheduled one overlaps with the one currently running, it will be skipped until there are no more warmings.

I think I will add a table so you can see more clearly at what time the next interval run is scheduled and whether it was skipped or not, and maybe even a setting to move it. Because the current implementation of attaching the next interval run to the time the setting was saved is very crude and non-transparent.

P.S. Your question made me look into the code of the plugin and I realized that the current interval functionality does not work properly. I will release the fix in ~1 hour. Please stay tuned and update the plugin on your sites when it arrives. Sorry for the inconvenience and let me know if you have any questions or suggestions.

Thanks!!

Not sure if it’s still relevant but this is what I get by setting the autorun interval at 1440 minutes (i.e. 24-hr)

View post on imgur.com

@loyukfai yeap, 1440 minutes is 24 hours. It looks correct to me. A new warming starts every 24 hours, and therefore a new log entitiy for it is created.

Or maybe you want me to clarify something for you? Feel free to ask, I will be happy to answer all your question.

The start time seems to be drifting?

Anyhow, when the specify time to run setting is implemented (Specify Time to Run? | www.remarpro.com), this would be a null issue. ??

Cheers.

@loyukfai

About time drifting: this is how Action Scheduler works, it has some kind of an enqueue to run tasks in the background, so the drifting is expected to happen. It actually will even happen with the scheduler run time you requested. The drifting is about 1h, based on the number of the tasks in the enqueue (if curious, you can see it on this page: /wp-admin/tools.php?page=action-scheduler&status=pending). And I have no control over it, unfortunately.

The feature you requested solves another issue: transparency. If you request it to run every Monday at 12:00 then you can expect the warming to happen at about this time.

I will work in this direction this month, it’s a very useful feature.

The first thing I want to do is to add transparency to the current interval logic, I think I will make a table with columns like:

Scheduled to run at | Run at | Status (pending, completed, skipped (because another warm was running)) | Link to the log

And I also want to add an option to shift the run time. Because currently it’s attached to the time you save the interval setting on, which is very opaque and inconvenient.

Maybe that will even be enough to suit your use case (e.g. run warming every Monday at 12:00).

But scheduling I suppose will be more about non-symmetric one-time runs. E.g. schedule on: Jul 1 12:00, Jul 2 15:00, Jul 5 19:00

I think this is not what you actually want, but rather a transparent interval with the option to shift it will be a better option for your needs.

Wow, very cool, thanks a lot!