TOO_MANY_CHANGES - Actual threshold?

[Sam Green]

Hi,

The TOO_MANY_CHANGES error when pulling from CustomerSyncService is clear, however, what exactly is the limit here? That is - how many changes are required to actually trigger this error?

Thanks

Sam

[Teja Makani]

Hello Sam,

The TOO_MANY_CHANGES error occurs when there are too many changed entities to return. You could try narrowing down the date range and request again, please note that CustomerSyncService supports historical changes for the last 90 days only. If the error persists, assume everything has changed and use each campaign data services's get requests to retrieve the most recent campaign data. Please let me know if you have any further questions.

We are running an annual developer feedback survey. Please take opportunity to leave feedback on how we can make managing campaigns at scale even easier.

Regards,
Sai Teja, AdWords API Team.

[Sam Green]

Hi ,

Thanks for your response. I understand the error - but how many changes are required to trigger it? 1,000? 10,000?

Thanks

Sam

[الشيخ الروحاني الحاج رشيد الكندي‎]

TOO_MANY_CHANGES - Actual threshold?

[Nadine Sundquist (AdWords API Team)]

Greetings Everyone,

I know this may sound odd, but there isn't a hard number the last time I checked on this, which was pretty recently. It's dependent on a number of factors such as the size of the change coming back or how expensive or complicated the change is that you are requesting coming back. The idea of this error is that if you get it., you should have error handling in place to catch the error and then reduce the date range that you are requesting coming back to parse the data into smaller date ranges. There isn't a constant in our system that magically sets this; it's a dynamic calculation based on a number of factors.

Cheers,

Nadine, AdWords API Team

On Wednesday, October 31, 2018 at 4:16:05 PM UTC-7, الشيخ الروحاني الحاج رشيد الكندي wrote:

TOO_MANY_CHANGES - Actual threshold?

[Sam Green]

Great - thank you for confirming