The Symptom: A contact’s membership or IIA (Individual Identifier/agent) record was changed in GrowthZone, but in CoreLogic the synced data shows as pending — the change does not appear to have been picked up.
The Root Cause: When GrowthZone sends a change to CoreLogic, there are two scenarios you may see:
- Scenario 1 — CoreLogic does not pick up the first attempt, then GrowthZone retries successfully. The sync is sent to CoreLogic, CoreLogic does not pick up the change, and GrowthZone retries and succeeds. A good example is Jeannie Mayfield, whose sync was originally sent on 5/2 but was not accepted by CoreLogic until a second attempt on 5/3 — see this screenshot of her sync.
- Scenario 2 — the data pushes once and CoreLogic does not pick it up. GrowthZone sends the data initially but CoreLogic does not pick it up, and historically GrowthZone did not resend. An example is Donna Munson — the data was sent on the 2nd but there was no second attempt; see this screenshot.
The Fix
Follow these steps to resolve the issue:
- A change has been released by the Development Team that adds more logic for the system to retry more often when CoreLogic does not pick up the initial data. With this fix in place, records that previously stalled in Scenario 2 will now be resent automatically.
- To review a contact’s CoreLogic sync history and confirm whether retries are occurring, go to Settings, Real Estate Edition section.
- Locate the affected contact and open their sync detail to view each send attempt and its timestamp. You can see the fix in action with Robert Marquardt — the following screenshot shows the multiple attempts GrowthZone made to send the information to CoreLogic before it was picked up on the 16th: view screenshot.
- Allow up to one day for the resend logic to complete. The sync should not take that long, but the additional retry attempts give CoreLogic more opportunities to accept the data.
Verification: How to know it worked Confirm the contact’s record in CoreLogic is no longer showing as pending and reflects the updated data. If you do not see the sync happen within a day, reply to your support contact with the new example so the team can investigate further with CoreLogic and help them accept the records more quickly.