Currently, we are using the Salesforce Suite to pull three different objects, all with their own mappings. Accounts & Assets pull once per hour on a standard cron run, while Related Addresses pull once per day (overnight) on a standalone URL process instead.
We are noticing instances where the last "deleted" date for our standalone queue is being influenced by the standard cron-run process when it seems like it shouldn't be, since this particular mapping does not run on cron:
The top part of the above image notes the correct time where our standalone URL queue queried a pull from SF to Drupal overnight. The bottom part, however, is showing a date and time from when Drupal's cron last run via the other mappings, despite the fact that we have cron runs disabled for this particular mapping (we are using the Check this box to disable cron pull processing for this mapping, and allow standalone processing via this URL option instead).
Is there a way to keep the deleted date independent here? We are occasionally missing instances of deletion because of this, and aren't sure if this is a bug, or if we're missing a configuration of some sort here.
Closed: duplicate
5.0
salesforce_pull.module
Yes, this could probably use some work.
My priority around delete queue is an overhaul, started here: 📌 Convert delete handling into a queue Needs work
This request should get rolled up into that work.