Contrib.social

Salesforce data updates not syncing via cron, only manual force pulls update existing records in Drupal

Open on Drupal.org →
Created on 3 October 2024, 12 months ago

Problem/Motivation

When using the Salesforce module to sync data between Salesforce and Drupal, updates to existing Salesforce records are not reflected in Drupal unless a manual force pull is performed. While new users are created when a record is added in Salesforce, updates to existing users are not being synced automatically via cron. Attempts to sync using both cron and the standalone queue have produced the same results: updates only occur when manually triggered. This creates a gap in synchronization for existing records, as Drupal does not reflect the latest changes from Salesforce unless a manual intervention is made.

Steps to reproduce

1. Set up the Salesforce module with cron-based synchronization.
2. Update an existing user record in Salesforce.
3. Wait for the scheduled cron run to trigger the pull operation.
4. Check the corresponding Drupal user record to see if the updates from Salesforce are reflected.
5. If the updates are not reflected, manually force-pull the updated record from Salesforce and check the Drupal user record again.

Proposed resolution

Investigate why automatic updates to existing Salesforce records are not being pulled by cron or the standalone queue. Ensure that the cron and queue mechanisms are correctly fetching updates to existing records. If any specific settings or configurations are required, document those clearly for users to avoid confusion. Also, check if there is a mismatch in how the pull operations are handled between new and existing records.

Remaining tasks

- Debug why cron and queue operations are failing to update existing user records.
- Identify if additional configuration is needed for updating existing records versus creating new ones.
- Document findings and provide guidance on settings or adjustments that need to be made.
- Test to ensure that after fixes, updates from Salesforce reflect correctly in Drupal without manual intervention.

User interface changes

No anticipated user interface changes.

API changes

No API changes expected at this time.

Data model changes

No changes to the data model are expected.

💬 Support request
Status

Active

Version

5.1

Component

salesforce_pull.module

Created by

🇺🇸United States rishi kulshreshtha

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @rishi kulshreshtha
  • Comment 6 months ago →
    🇺🇸United States coconnor

    I can't offer a programmatic solution, but I did find a way to trigger the pull without using the UI (with help from @cosmicdreams on the #salesforce channel...)

    1. Ensure "Provide standalone queue processing endpoint and disable cron processing" on /admin/config/salesforce/settings is disabled.
    2. Run cron as usual (Full disclosure: I'm leveraging Ultimate Cron → for our cron jobs, but I see no reason why vanilla Drupal cron wouldn't work similarly.)
    3. After the cron run, the cron_salesforce_pull queue should be updated as expected. (I use Queue UI → to monitor that.)
    4. Run drush queue:run cron_salesforce_pull on the instance. Content should be updated.

    For the short term, I may just use a script/crontab combo to kick off the Drush part of this. But it would suuuure be nice to have the job run without the hackiness of this solution :)

  • Comment 26 days ago →
    🇺🇸United States armyguyinfl Florida

    Can someone assist why you would see 2 pull_create entries in the salesforce mapped object when it already exists and the timestamps are similar. In ~10% of the cases, pull updates are failing to update and leave the data stale. We have 2 cron jobs running.

    1. Load opportunity queue: sf_drush opportunities (custom script that calls command)
    2. Process pull queue: cron_salesforce_pull (salesforce command)

    id,revision_id,salesforce_mapping,salesforce_id,created,changed,entity_updated,last_sync_status,last_sync_action,revision_created,revision_user,revision_log_message,revision_default
    2311126,42465446,opportunities,00---redacted--AZ,1755533810,1755533810,1755533810,1,pull_create,1755533810,0,,1
    2311126,42466626,opportunities,00---redacted--AZ,1755533810,1755540246,1755540246,1,pull_create,1755540246,0,,1
    2311126,42466631,opportunities,00---redacted--AZ,1755533810,1755540246,1755540246,1,pull_update,1755540246,0,,1

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024