Re: UNAUTHENTICATED for Google Ads API
We're seeing the same errors across roughly 5% of our calls relating to
offlineUserDataJobOperations. We're still running the v12 version of the
API through Node.js.
This is also reported in the cloud console where our api is registered. It
started on the 31st
It's happening for the endpoints:
/AddOfflineUserDataJobOperations
/CreateOfflineUserDataJob
/RunOfflineUserDataJob
We also made no changes to our systems or code.
On Friday, September 1, 2023 at 10:00:09 PM UTC+2 sheryan...@braze.com
wrote:
> Hi! Seeing the same issue using the ruby client. Started yesterday around
> 12 PM EST. Also happening in a transient manner. I have also sent an email
> to support.
>
> On Friday, September 1, 2023 at 3:48:52 PM UTC-4 Troy Banks wrote:
>
>> And for what it's worth, I have a request Id for one of the failed
>> requests if that's necessary for troubleshooting
>>
>> On Friday, September 1, 2023 at 3:45:47 PM UTC-4 Troy Banks wrote:
>>
>>> Hi, starting over the past day or so, we've started getting intermittent
>>> errors from the Google Ads API when trying to add users (operations) using
>>> an OfflineUserDataJobServiceClient from the Java SDK. Nothing has changed
>>> in our codebase nor with our authentication as far as I'm aware. I don't
>>> see an outage or anything of that sort being reported on the status
>>> dashboard. The errors don't happen for every request, but it happens enough
>>> that it prevents us from completely uploading the intended user list size
>>> of 1M+. It's my understanding correct that the Java SDK should refreshing
>>> the credentials when necessary, so I'm confused why we'd get this error all
>>> of a sudden. Thanks for any help
>>>
>>> The request details from logs:
>>>
>>> MethodName:
>>> google.ads.googleads.v13.services.OfflineUserDataJobService/AddOfflineUserDataJobOperations
>>> Endpoint: googleads.googleapis.com:443
>>> Headers: {developer-token=REDACTED, login-customer-id=REDACTED,
>>> x-goog-api-client=gl-java/11.0.19 gccl/25.0.0 gapic/25.0.0 gax/2.22.0
>>> grpc/1.52.1 pb/3.21.12}
>>>
>>> And the error we've been seeing
>>>
>>> UNAUTHENTICATED, Fault: Request is missing required authentication
>>> credential. Expected OAuth 2 access token, login cookie or other valid
>>> authentication credential. See
>>> https://developers.google.com/identity/sign-in/web/devconsole-project
>>>
>>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/955fbf44-7de2-41b3-a378-57d9b202499fn%40googlegroups.com.
INVALID_TOKEN_HEADER error since last night(started on 10th of april)
Hi! Since last night, the following request causes an INVALID_TOKEN_HEADER. These requests did not cause an error before last night: http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="https://adwords.google.com/api/adwords/rm/v201802; xmlns:jaxb="http://java.sun.com/xml/ns/jaxb; xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;> https://adwords.google.com/api/adwords/rm/v201802; xmlns="https://adwords.google.com/api/adwords/rm/v201802;> __our_user_agent__ __our_developer_token__ __our_client_customer_id__ https://adwords.google.com/api/adwords/rm/v201802;> https://adwords.google.com/api/adwords/cm/v201802;>Id https://adwords.google.com/api/adwords/cm/v201802;>Name https://adwords.google.com/api/adwords/cm/v201802;>Status https://adwords.google.com/api/adwords/cm/v201802;>SizeRange https://adwords.google.com/api/adwords/cm/v201802;>IsReadOnly Name EQUALS bcdefghif Status EQUALS OPEN ListType EQUALS CRM_BASED REMARKETING The following request does _not_ cause an error: http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="https://adwords.google.com/api/adwords/mcm/v201802; xmlns:jaxb="http://java.sun.com/xml/ns/jaxb; xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;> https://adwords.google.com/api/adwords/mcm/v201802; xmlns="https://adwords.google.com/api/adwords/mcm/v201802;> __our_user_agent__ __our_developer_token__ __our_client_customer_id__ https://adwords.google.com/api/adwords/mcm/v201802;> https://adwords.google.com/api/adwords/cm/v201802;>CustomerId https://adwords.google.com/api/adwords/cm/v201802;>Name https://adwords.google.com/api/adwords/cm/v201802;>AccountLabels ExcludeHiddenAccounts EQUALS true We have not changed the code in any way, nor changed the developer token in the API centre. Hopefully you can help us explain what is causing these errors and why they started showing up yesterday. We're also wondering why some requests do work and others don't. Regards and thanks, Ate p.s. I tried posting this issue earlier but didn't see the topic in the forum, so I've resubmitted this. If that is problematic please remove one of the two topics -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords 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 "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/2e1f817b-9f13-4d32-867d-33e5420bf1bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Getting QuotaCheckError.INVALID_TOKEN_HEADER Error for some requests since April 10
Hi! We have a connection between our SaaS product and Google Adwords running for several customers. It runs a daily export to Adwords. Starting last night, the exports started failing with a `INVALID_TOKEN_HEADER` error. There has been no change in our code between the last correct export and the failing export and we haven't changed any settings in the API centre. Furthermore, some requests still occur correctly and others don't. For example this request is handled correctly: http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="https://adwords.google.com/api/adwords/mcm/v201802; xmlns:jaxb="http://java.sun.com/xml/ns/jaxb; xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;> https://adwords.google.com/api/adwords/mcm/v201802; xmlns="https://adwords.google.com/api/adwords/mcm/v201802;> __our_user_agent__ __our_developer_token__ __our_client_customer_id__ https://adwords.google.com/api/adwords/mcm/v201802;> https://adwords.google.com/api/adwords/cm/v201802;>CustomerId https://adwords.google.com/api/adwords/cm/v201802;>Name https://adwords.google.com/api/adwords/cm/v201802;>AccountLabels ExcludeHiddenAccounts EQUALS true And this request causes an error: http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="https://adwords.google.com/api/adwords/rm/v201802; xmlns:jaxb="http://java.sun.com/xml/ns/jaxb; xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;> https://adwords.google.com/api/adwords/rm/v201802; xmlns="https://adwords.google.com/api/adwords/rm/v201802;> __our_user_agent__ __our_developer_token__ __our_client_customer_id__ https://adwords.google.com/api/adwords/rm/v201802;> https://adwords.google.com/api/adwords/cm/v201802;>Id https://adwords.google.com/api/adwords/cm/v201802;>Name https://adwords.google.com/api/adwords/cm/v201802;>Status https://adwords.google.com/api/adwords/cm/v201802;>SizeRange https://adwords.google.com/api/adwords/cm/v201802;>IsReadOnly Name EQUALS __some_name__ Status EQUALS OPEN ListType EQUALS CRM_BASED REMARKETING This causes me to suspect the AdwordsUserList service as a culprit. But I can't explain why the above request would function correctly two days ago, and stop failing with a INVALID_TOKEN_HEADER error yesterday. Hopefully you can help me shed light on this topic. I've replaced our userAgent, developerToken and clientCustomerId with other values in the two posted requests. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords 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 "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/0697b013-6fa2-4d1d-bfd0-c35b4bd22e7e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
