Closed jonathanstegall closed 3 years ago
Locally on my laptop, according to the /wp-admin/tools.php?page=action-scheduler
URL indicator that migration is still happening, the migration started at 9:45am and finished at 10:25am. No other WordPress tasks were happening. As far as I can tell, it didn't run into any errors but I have no idea what it may have missed getting from Salesforce, for example.
It seemed like it didn't run any of the plugin's scheduled tasks until I went to the plugin schedule settings and changed the frequency (from 5 to 10 minutes, though I then changed it back to 5). Perhaps it had to recreate something.
If this is the case, we should try to include this in the plugin when it realizes the version change, but I'm not really sure when it should do that. It might also have been a fluke in my case, but I do think that is unlikely.
It didn't run after that on schedule, just a manual pull. So I think I might also have had a cron problem locally. I installed WP-Crontrol, and then it started running plugin tasks as I would have expected.
I think this got significantly more reliable on my laptop with version 3.2.0. I'm not sure why that is though.
GitHub API communication error. Please contact a human. (commit-ID: 6ec4839b1e9e91f36488428a9c8770329ad4cf3f).
What does this Pull Request do?
When it is merged, this pull request will close #299 and upgrade our installation of the ActionScheduler library to version 3.2. This will start several processes that the library runs to upgrade itself. Read about that process on their site.
How do I test this Pull Request?
/wp-admin/tools.php?page=action-scheduler
URL in your WordPress install after checking out this branchwp_actionscheduler_actions
,wp_actionscheduler_claims
,wp_actionscheduler_groups
, andwp_actionscheduler_logs
(current as of 5/19/21).