Numerous posts have identified what appears to be a bug with excluding countries. It appears to be limiting to 122. We are seeing this with the API, the offline tool, and the web interface.
To reproduce, try to bulk add all 217 countries (all but US) to a campaign's excluded locations. It will fail with the message "The number of entities exceeds the limit". It will continue to fail until you reduce the list to 122. Please escalate this to the appropriate devs to investigate. On Tuesday, March 5, 2024 at 6:54:08 PM UTC-5 Google Ads API Forum Advisor wrote: > Hi, > > Thank you for reaching out to the Google Ads API support team. > > After reviewing your concern, I understand that you are encountering the " > RESOURCE_LIMIT > <https://developers.google.com/google-ads/api/reference/rpc/v16/ResourceCountLimitExceededErrorEnum.ResourceCountLimitExceededError#resource_limit>" > error > while trying to set location data for a new campaign via the Google Ads API. > > The "RESOURCE_LIMIT > <https://developers.google.com/google-ads/api/reference/rpc/v16/ResourceCountLimitExceededErrorEnum.ResourceCountLimitExceededError#resource_limit>" > error > means the request is attempting to create a resource that would cause the > total number of those resources to exceed a specified limit. Kindly note > that there are multiple limits on the number of resources that can exist in > certain contexts. So, identify the limit that's being encountered by > reviewing System limits > <https://developers.google.com/google-ads/api/docs/best-practices/system-limits>. > > Either reuse an existing resource, or remove resources to create space for > new ones. > > Also, in order to investigate the issue further, kindly provide us with > the "complete" API logs (request > <https://developers.google.com/google-ads/api/docs/concepts/field-service#request> > and response > <https://developers.google.com/google-ads/api/docs/concepts/field-service#response> > with request-id > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id> > and request header > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers>) > > generated at your end. > > If you are using a client library and haven't enabled the logging yet, I > would request you to enable logging for the specific client library that > you are using. You can refer to the guides Java > <https://developers.google.com/google-ads/api/docs/client-libs/java/logging> > , .Net > <https://developers.google.com/google-ads/api/docs/client-libs/dotnet/logging> > , PHP > <https://developers.google.com/google-ads/api/docs/client-libs/php/logging> > , Python > <https://developers.google.com/google-ads/api/docs/client-libs/python/logging> > , Ruby > <https://developers.google.com/google-ads/api/docs/client-libs/ruby/logging> > or Perl > <https://developers.google.com/google-ads/api/docs/client-libs/perl/logging> > to > enable logging at your end. For REST interface requests, you can enable > logging via the curl command by using the -i flag. > > You can send the details via *Reply* *privately** to the **author* > *option*, or *direct** private **reply* to this email. > > > This message is in relation to case "ref:!00D1U01174p.!5004Q02rzhk6:ref" > > Thanks, > > [image: Google Logo] Google Ads API Team > > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/d6f37572-df7e-4415-af01-5a33a751bfe3n%40googlegroups.com.