Thank you for the response.
Several things:
1. The error only occurs for this particular query. All other queries work
fine. The overall process run reporting tasks on a regular basis with no
issues. The code itself runs perfectly when a different query is provided,
even for the same resource, without the desired segements.
2. I've attempted this request via curl locally, and I am still receiving
an internal error:
[{
"error": {
"code": 500,
"message": "Internal error encountered.",
"status": "INTERNAL",
"details": [
{
"@type":
"type.googleapis.com/google.ads.googleads.v15.errors.GoogleAdsFailure",
"errors": [
{
"errorCode": {
"internalError": "INTERNAL_ERROR"
},
"message": "An internal error has occurred."
}
],
"requestId": "CTtg8hIqUYtP4OIGZc5DPA"
}
]
}
}
I've added a redacted screenshot of the output for reference. AS you can
see - the same code runs well for a different query (stored in a query.json
file), but fails to run when the query is modified.
3. Updating the module as suggested produces the same error.
Thoughts?
On Tuesday, November 7, 2023 at 3:48:40 PM UTC+2 Google Ads API Forum
Advisor wrote:
> Thanks for the data.
>
> I saw that in your first interaction, provided the campaign id. If this is
> the one the consistently returns the error, please confirm.
>
> The error indicates that grpc has encountered an error and provided the
> stacktrace that is in the logs. This only indicates that an invariant has
> changed which doesn't point us to the core of the problem.
>
> When we run the query internally with your credentials, it succeeds. This
> is evidence that it is likely not a data problem.
>
> Since the error occurs in grpc, the RPC framwork, it indicates a problem
> of communication between your side and our sever. The next debugging steps
> are:
>
> - Determine if the error only occurs for this query with specific
> values or if this query fails with all values. Values here indicates
> campaign and insight.
> - Attempt a failing query using Curl with the the command line option
> -i. This will bypass the grpc client layer.
> - Upgrade to the latest versions of grpcio and grpcio-status.
>
> You can upgrade the versions of the two grpc packages with: python -m pip
> install --upgrade grpcio==1.56.2 grpcio-status==1.56.2
>
> Let me know the outcome of the tests.
>
>
>
> This message is in relation to case "ref:!00D1U01174p.!5004Q02q9T1G:ref"
>
> Thanks,
>
> [image: Google Logo]
> Bob Hancock
> 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/88da6369-f81c-4115-8b34-fa0e3df28a17n%40googlegroups.com.
