Salesforce updates not pulling through

You might want to install the WP Crontrol plugin and see if your cron jobs are working correctly. You can also check on the Scheduled Actions tab (/wp-admin/tools.php?page=action-scheduler) and make sure that ActionScheduler is working correctly.

Finally, I’m hoping to release a version 2.0.0 in the next week or so with an upgraded version of ActionScheduler. If you’d be willing to test it and see if that helps (preferably on a staging site first!), you can access it at https://github.com/MinnPost/object-sync-for-salesforce/pull/404.

There are several custom cron events running on the site successfully every hour (WP Crontrol has been installed since build during March/April to manage these, and is still installed), but ActionScheduler seems to be missing events. The cron has been moved to a server cron, so no longer relies on site hits to run.

Salesforce is also populating 2 sites with identical content (one launched last year and updates correctly).

Are you saying this plugin runs on two different sites from the same Salesforce instance? It doesn’t seem to me like that would go well; I certainly wouldn’t provide support for it. I can’t speak to whether the site would work with a server cron, you might want to ask the ActionScheduler people about that.

The final thing I’d ask is if you’ve turned on debug mode. It creates a lot of log entries, but at least if you run it for a bit you can check and see if it’s running the Salesforce API queries that you expect it to be running.

Different Salesforce instances (with different callback URLs), but same Salesforce account pulling same object from Salesforce.

It has previously been working fine, and last new post was pulled on 22nd June.

Changes to data on some posts does go through correctly, but not on others, and there have been no new posts since this date although new items have been added to Salesforce.

Since around the same time the Salesforce mapping page does not load fully – inspecting the WP field select option, it’s pulling through ACF fields that are in a different post type which it didn’t do before.

I think maybe investigate whether ACF has changed something since then, and if so the more specifics you can give the better. This plugin was last updated in May, although I imagine ACF has been updated more recently. Generally this plugin does work with ACF, although I’ve seen some cases where it doesn’t because of something ACF is doing. If you can determine that there’s a bug, or exactly how to reproduce it, I can look into it.

And again, there’s an update I’m planning to release soon, so if you’ve got the capacity, you might test it and see if it still has the same issue. If it’s ACF-specific, it’s probably not very likely that the new version will have an impact on it. But if it’s related to ActionScheduler, it’s very possible that it will.

ACF hasn’t changed anything that would affect this – I didn’t have access to the admin of the site over the weekend, but there have no new posts since May 22nd – is this when the plugin was last updated? Have the recent changes for V2 been pushed in 1.10?

Around the same time, fields in the Field mapping area have not been loading (https://pasteboard.co/KaO9y7z.png) – Is this related?

There are certainly no V2 changes in 1.10. 1.10 came out on May 14, so I think it’s possible that it is the cause. Users had reported that the plugin setting for whether Salesforce fields showed the field label or the API name was not working. I’m talking about the Salesforce Field Display Value field.

I’m wondering if there are certain Salesforce cases where the fix in 1.10 caused problems. I haven’t seen this happen, but it seems possible.

1. What is the current value you are using for that Salesforce Field Display Value field?
2. If you change it to whatever the other option is, does it work correctly?

Current value is Field Label, no change when set to API Name.

Okay. Well, I don’t have any other ideas to offer you, at this point, and I haven’t been able to reproduce it. You might try downgrading to version 1.9.9 and see if you can identify what exactly has caused the problem. The only other change in version 1.10.0 was to include an ACF front end hook for users who run front-end forms. To the best of my knowledge that does not run on the back end.

In any case, if it’s not possible to identify a reproducible cause, it’s likely that whatever it is will persist when version 2.0.0 comes out (which hopefully will be soon).

It’s currently running on 1.9.9, but still has issues – would staging site access help with debugging?

Not for me at least, I don’t have the capacity for that kind of work.