Data are not pulled from SF

I’d like to learn if this is related to another issue people are reporting in version 2.1.

First, what version of PHP are you using on your server? Do you see any error logs on your server, or relevant log messages from the plugin?

If not, to see if it’s a 2.1 issue, can you revert to version 2.0.3 and see if this continues to happen?

@jonathanstegall Thank you for quick response. So PHP version 7.4.27 (Supports 64bit values). No errors connected with cron, scheduling tasks etc. About previous plugin version, well i will try to downgrade plugin to check difference

@jonathanstegall So after few days of tests i could say that plugin version doesn’t have any influence on this problem and in version 2.0.3 this problem also exist. It looks for me that problem somehow connected with scheduling task because changing of “Run Schedule Every” field value force plugin to start working again. Let me know please if you have any idea how it could be fixed. But also, i want ask you if this plugin has any hook which i could use for updating “Run Schedule Every” field value with code? Maybe in that cause if i will create another cron task which will update this value regularly then it could be temporary solution of this problem. Also, i think about creating manually cron function which should run plugin function that do all stuff connected with API calls to SF, so could you let me know function should i call for this?

@jonathanstegall wanted to let you know that we’re experiencing a very similar issue as @wolfage. Successfully mapped objects are only pulling in after we update the “Run Schedule Every” setting, however, it’s only pulling in 11 records at a time.

We’re also seeing this php error – “NOTICE: PHP message: PHP Warning: ignore_user_abort() has been disabled for security reasons in /wordpress/wp-cron.php on line 19”. Maybe that’s what’s causing the scheduler from making calls…

This seems like something to work with your host on to me. Action Scheduler (the scheduling library) says it is able to work with schedulers that aren’t WP Cron, but this isn’t something I would provide support for.

Update: Updating the “Run Schedule Every” still only pulling in 11 records at a time after updating the setting but it appears to be creating duplicate objects in WordPress.

Also, FYI, we’re triggering blank updates on the records in Salesforce in order to get existing SF data to pull into WordPress.