Getting Intermittent "CustomerSyncError.TOO_MANY_CHANGES" response for the same requested time frame

[Giles Bodger]

Hi all,

Question on having to full sync because of "too many changes" error

We have an implementation that for many accounts will try to do a sync every 15 minutes for the latest changes since the previous sync. This has been running fine for the last 3 years or so, but i have noticed recently where we appear to be requesting a full sync for an account where we haven't made any changes.

Our logic is such that if we get told there are too many changes to sync on an account for a given timeframe then we halve the timespan and ask again, if there are still too many changes we halve again and so on, down to where we have asked for changes for the 1 second since the last sync and we are STILL getting the too many changes error - and in this case we simply request a full sync.

So, i have had these couple of occasions where the application is forced down the path of running a full sync, BUT if i then take the original "to" and "from" times used in the reducing time span calculation and debug the sync application locally, i CAN get the changes since the last sync timestamp.

Is this possible? Could the same "to" and "from" timestamp be used against the API for the same account and get different responses as to whether there are too many changes to sync in the given timespan ?

A weird one, but many thanks in advance

Giles

[Yin Niu]

Hi Giles, 

Could you send SOAP log for the requests that have different output? Please also include your clientCustomerID. Click Reply privately to author in the forum when responding. 

Thanks,

Yin, AdWords API Team.