Change History Report Issue While fetching more than 10K Rows.

[Shipra]

Hi There,
I am facing issues while fetching more than 10K rows from change_events report, This doc suggests:  to store timestamp of last row and start from there. 
But this is not working when "change_date_time" is same for ~ 10K rows. So every time we end up getting same set of result, and increasing the time by few seconds is not a solution as we might miss the changes applied at exact same time.
So could you suggest any other way to fetch more than 10K rows? Something like pagination or anything else?

I can see one related thread: https://groups.google.com/g/adwords-api/c/hSKgtXy1D9g
But didn't get solution from there.

Thanks,
Shipra.

[Google Ads API and AdWords API Forum]

Re-posting the last inquiry (https://groups.google.com/g/adwords-api/c/eLGvVQfqbzE) from the forum as it wasn't routed to our support queue.

Regards,
Google Ads API Team

[Google Ads API and AdWords API Forum]

Hi Shipra,

Thank you for raising this concern to the Google Ads API team.

In order for us to further investigate, we would need the complete request and response logs with request-id. Once these are available, kindly provide it to us so we can proceed with our investigation. If you haven't configured logging yet, you may do so by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link.

You may then send the requested logs via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Reference links:

• request - https://developers.google.com/google-ads/api/docs/concepts/field-service#request
• response - https://developers.google.com/google-ads/api/docs/concepts/field-service#response
• request-id - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id
• link - https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging

Regards,

Google Ads API Team

On Monday, May 15, 2023 at 7:12:09 PM UTC+8 Shipra wrote:

[Nay Win]

hi@gmail

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwor...@googlegroups.com
To unsubscribe from this group, send email to
adwords-api...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/58cb0390-f47d-4146-9f49-105b3afa4606n%40googlegroups.com.

[Google Ads API Forum Advisor]

Hi there,

Thanks for commenting on this Forum thread. Can you confirm if you are having similar issues to what Shipra reported in this thread? You may provide more details on your concern so that we can assist you further.

This message is in relation to case "ref:_00D1U1174p._5004Q2lJcos:ref"

Thanks,
 

Google Ads API Team