• Resolved esowers

    (@esowers)


    I’m setting up a new site to sync records. On the salesforce side we have about 4,000 records that get updated frequently by salesforce tasks. This initiates a sync to WordPress. However I’m running into an issue with the WordPress Scheduled Actions not keeping up with the pull_process_records tasks. I currently have about 6500 pending actions and that’s not going down at all.

    I see the options in the plugin for changing pull query limit, batch size and concurrent batches. However when I increase those it doesn’t seem to allow more than 20-40 records to be processed at a time. I read the documentation on Action Scheduler’s website and they said turning concurrent batches to 0 would process everything, however it doesn’t look like that works in this instance.

    Can you give any pointers on what I might be missing? I have the wp-cron scheduled to run every 5 minutes as a server scheduled task.

    Thanks!

    • This topic was modified 4 years ago by esowers.
Viewing 4 replies - 16 through 19 (of 19 total)
  • Thread Starter esowers

    (@esowers)

    @tnolte I’d love to hear more about your project too. We’re working on rolling out a salesforce WordPress portal as well for our donors and various committees. Shoot me an email or something as I’d love to hear more. [email protected]

    @esowers yeah, the project I’m working on is to setup a WordPress Portal where users can login and manage a restricted set of Salesforce data. There are multiple users per Salesforce Account with different levels of access. All management is done via the WordPress Dashboard with a customized experience. I’d be happy to share more details on what I’ve accomplished. I’ll shoot you an email.

    Plugin Author Jonathan Stegall

    (@jonathanstegall)

    Well, if either of y’all are inclined to test, I’ve made a version of the plugin that does nothing but upgrade ActionScheduler. You can install it via the pull request. I’ve run it locally, but I haven’t watched it closely and haven’t really inspected what is happening afterwards yet, so do be very careful of course and take backups and so on. But if you’ve got capacity to identify possible issues, any testing would be appreciated!

    I’ll have to see if I have some time, and environment to try to test that out. I’m curious, about the Concurrent Batches setting with the scheduler. It seems as though it doesn’t really do anything. I’ve got it set to 10 but from what I see in the Scheduler concerning how many actions are queued up there were only like 150, and my actions for each batch is like 200. So basically I got only 1 batch ever running. And it doesn’t seem to matter what I set this number to.

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘Sync throughput’ is closed to new replies.