Hello,
we are now running into an Internal Error when fetching product_group_view
data for another client:
Does it have the same problem with corrupt product partitions?
*Here are the request/response logs incl. request-id:*
Method Name:
/google.ads.googleads.v14.services.GoogleAdsService/SearchStream
Host: googleads.googleapis.com
Headers: {
"x-goog-api-client": "gl-php\/8.0.30 gccl\/19.2.0 gapic\/19.2.0
gax\/1.18.2 grpc\/1.50.2 rest\/1.18.2 pb\/+n",
"x-goog-request-params": "customer_id=8875125139",
"developer-token": "REDACTED",
"login-customer-id": "4554523147"
}
Request:
{"customerId":"8875125139","query":"\n SELECT
segments.date,\ncampaign.id,\nad_group.id,\nad_group_criterion.criterion_id,\nad_group_criterion.criterion_id,\nsegments.ad_network_type,\nsegments.device,\nmetrics.cost_micros,\nmetrics.clicks,\nmetrics.impressions,\nmetrics.impressions\n
FROM product_group_view\n WHERE
segments.date BETWEEN '2023-12-14' AND '2023-12-14'\n
AND campaign.status IN(ENABLED, PAUSED, REMOVED)\n AND
ad_group.status IN(ENABLED, PAUSED, REMOVED)\n AND
ad_group_criterion.status IN(ENABLED, PAUSED, REMOVED)\n
AND ad_group_criterion.listing_group.type = 'UNIT'\n AND
metrics.impressions > 0 AND segments.date = '2023-12-14' "}
Response
-------
Headers: {
"request-id": "I7uqA2oUyo_NYQHPRwWIiQ",
"date": "Fri, 15 Dec 2023 18:08:04 GMT",
"alt-svc": "h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000"
}
Fault
-------
Status code: 13
Details: Internal error encountered.
Failure:
{"errors":[{"errorCode":{"internalError":"INTERNAL_ERROR"},"message":"An
internal error has occurred."}],"requestId":"I7uqA2oUyo_NYQHPRwWIiQ"}
Exception in retryDecider: {
"message": "Internal error encountered.",
"code": 13,
"status": "INTERNAL",
"details": [
{
"@type": "google.ads.googleads.v14.errors.googleadsfailure-bin",
"data": "<Unknown Binary Data>"
},
{
"@type": "grpc-status-details-bin",
"data": "<Unknown Binary Data>"
},
{
"@type": "request-id",
"data": "I7uqA2oUyo_NYQHPRwWIiQ"
}
]
}
On Tuesday, November 14, 2023 at 2:58:46 PM UTC+1 Google Ads API Forum
Advisor wrote:
> I just spoke with my colleague and they cannot fix it on the back end. The
> workaround is:
>
> - Recreate the AdGroup.
> - Delete the original AdGroup that has the corrupted data.
> - Let me know the results.
>
>
>
> This message is in relation to case "ref:!00D1U01174p.!5004Q02pRLZH: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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/2aebb9fc-df01-4dcd-8ac5-8c9bf758ceebn%40googlegroups.com.
