You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Came across a scenario yesterday where I built a Smart List.
Was excitedly anticipating the data arriving in our destination.
It appears the stitch scheduled sync kicked off and started syncing the newly added smart list - but the smart list was still being 'processed' on the hubspot side. This means the smart list was being loaded with the contacts that met the criteria. This is done via some type of backend process on hubspot - and can take some time to complete.
The end result is that the synced membership on the destination was never fully populated.
The tap should look at the processing attribute and only sync lists where metaData->processing = 'DONE'
Came across a scenario yesterday where I built a Smart List.
Was excitedly anticipating the data arriving in our destination.
It appears the stitch scheduled sync kicked off and started syncing the newly added smart list - but the smart list was still being 'processed' on the hubspot side. This means the smart list was being loaded with the contacts that met the criteria. This is done via some type of backend process on hubspot - and can take some time to complete.
The end result is that the synced membership on the destination was never fully populated.
The tap should look at the processing attribute and only sync lists where metaData->processing = 'DONE'
https://developers.hubspot.com/docs/methods/lists/get_lists
{
"lists": [
{
"dynamic": true,
"metaData": {
"processing": "DONE",
"size": 161,
"error": "",
"lastProcessingStateChangeAt": 1477518645996,
"lastSizeChangeAt": 1479298304451
},
The text was updated successfully, but these errors were encountered: