Re: Getting QuotaCheckError.INVALID_TOKEN_HEADER Error for some requests since April 10
Hi All, This issue is resolved now and you are not expected to see any more failures. Please let us know if you are still encountering the INVALID_TOKEN_HEADER error. Thanks, Sreelakshmi, AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/430a02cd-d6f0-4723-b9eb-e7ee113e1683%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Getting QuotaCheckError.INVALID_TOKEN_HEADER Error for some requests since April 10
Hi All, Our team is actively working on fixing this issue. I will keep you posted on the updates. Thanks, Sreelakshmi, AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/08e9e07a-6e32-4c46-af4b-9b7afd0ef289%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Getting QuotaCheckError.INVALID_TOKEN_HEADER Error for some requests since April 10
Hello, same issue here. It started 6 hours ago. Only in AdwordsUserListService call. 5% times it works, 95% not. Others API call are ok. We did not change anything on our side. Best regards Juro. Dňa utorok, 10. apríla 2018 11:52:12 UTC+2 alexande...@emarsys.com napísal(-a): > Hi, > > we are seeing the same error and sometimes it works. We even re-generated > the developer token in the AdWords API Center but that didn't help. We also > didn't deploy any changes. For us it the issue started to happen at 18:11 > UTC yesterday (2018-04-09). > > Best, > Alexander > > On Tuesday, 10 April 2018 11:37:24 UTC+2, Ate Fokkinga wrote: >> >> >> 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: >> >> > xmlns:soapenv="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;> >> >> > xmlns:ns1="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;> >> >> > xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;>CustomerId >> > xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;>Name >> > xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;>AccountLabels >> >> ExcludeHiddenAccounts >> EQUALS >> true >> >> >> >> >> >> >> And this request causes an error: >> >> > xmlns:soapenv="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;> >> >> > xmlns:ns1="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;> >> > xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;>Id >> https://adwords.google.com/api/adwords/cm/v201802;>Name >> > xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;>Status >> https://adwords.google.com/api/adwords/cm/v201802;>SizeRange >> > xmlns:cm="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/2156279c-c09c-4766-b46d-f57216fdad12%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Getting QuotaCheckError.INVALID_TOKEN_HEADER Error for some requests since April 10
Hi, we are seeing the same error and sometimes it works. We even re-generated the developer token in the AdWords API Center but that didn't help. We also didn't deploy any changes. For us it the issue started to happen at 18:11 UTC yesterday (2018-04-09). Best, Alexander On Tuesday, 10 April 2018 11:37:24 UTC+2, Ate Fokkinga wrote: > > > 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: > > xmlns:soapenv="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;> > > xmlns:ns1="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;> > > xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;>CustomerId > xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;>Name > xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;>AccountLabels > > ExcludeHiddenAccounts > EQUALS > true > > > > > > > And this request causes an error: > > xmlns:soapenv="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;> > > xmlns:ns1="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;> > xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;>Id > https://adwords.google.com/api/adwords/cm/v201802;>Name > xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802;>Status > https://adwords.google.com/api/adwords/cm/v201802;>SizeRange > xmlns:cm="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/694c83d1-5cfd-4951-8c12-81706da7caaf%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.
