If you’ve been using WPCD For a while now you know that callbacks is how we push data from the server to the WPCD console. For example, the information in the HEALTH column in the server list is collected from the data sent by our callbacks processes. However, this only runs once per day.
Of course, you can change the schedule by logging into the server and using the CRONTAB command line tools to change the time at which the process will run. You can even add additional processes (eg: run it twice per day) But that’s still a little bit of a pain if you have a large number of servers.
With this new Powertools feature, you can setup a schedule that is different without logging into the server. And the core process will always run daily – anything defined here is in addition to that core process.
Also, there are some limitations that you should be aware of – read the NOTES section at the bottom of this document to understand what those are!
Note: Callbacks must be installed on the server for this feature to work. You can’t run them if they’re not already installed.
This will run callbacks FOR ALL SERVERS using the schedule you chose.
You can prevent the callbacks from running for any server. Each server has a new PERODICALLY RUN CALLBACKS metabox with an option to prevent the callbacks from running.
You can setup a custom schedule if one of the pre-installed ones are not suitable. WPCloudDeploy version 4.16 includes 4 pre-defined schedules
You can create one or more custom schedules on the WPCLOUDDEPLOY-> SCHEDULES screen. Just click the ADD NEW button at the top of the list.
One of the differences between this type of scheduling and the Core plugin is the way in which the schedule functions and triggers the backup. With the core plugin, a CRON is set on the server itself to trigger the callbacks. With this function, the WPCD WordPress Cron is used to trigger things. If, for some reason, the WPCD CRON isn’t working, then the callbacks will not be triggered.
You should allow for enough time for the callbacks to complete between scheduled runs. We do not recommend anything less than 15 minutes and even that might be too low. Running callbacks is an intensive process so running it often can use up server resources that your sites might need. This is one of those tools that you can use to shoot yourself in the foot if you’re not careful!