Getting QuotaCheckError.INVALID_TOKEN_HEADER Error for some requests since April 10

[Ate Fokkinga]

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:

<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope 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">
  <soapenv:Header>
    <ns1:RequestHeader xmlns:ns1="https://adwords.google.com/api/adwords/mcm/v201802" xmlns="https://adwords.google.com/api/adwords/mcm/v201802">
      <ns1:userAgent>__our_user_agent__</ns1:userAgent>
      <ns1:developerToken>__our_developer_token__</ns1:developerToken>
      <ns1:clientCustomerId>__our_client_customer_id__</ns1:clientCustomerId>
    </ns1:RequestHeader>
  </soapenv:Header>
  <soapenv:Body>
    <get xmlns="https://adwords.google.com/api/adwords/mcm/v201802">
      <serviceSelector>
        <cm:fields xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802">CustomerId</cm:fields>
        <cm:fields xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802">Name</cm:fields>
        <cm:fields xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802">AccountLabels</cm:fields>
        <cm:predicates>
          <cm:field>ExcludeHiddenAccounts</cm:field>
          <cm:operator>EQUALS</cm:operator>
          <cm:values>true</cm:values>
        </cm:predicates>
      </serviceSelector>
    </get>
  </soapenv:Body>
</soapenv:Envelope>

And this request causes an error:

<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope 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">
  <soapenv:Header>
    <ns1:RequestHeader xmlns:ns1="https://adwords.google.com/api/adwords/rm/v201802" xmlns="https://adwords.google.com/api/adwords/rm/v201802">
      <ns1:userAgent>__our_user_agent__</ns1:userAgent>
      <ns1:developerToken>__our_developer_token__</ns1:developerToken>
      <ns1:clientCustomerId>__our_client_customer_id__</ns1:clientCustomerId>
    </ns1:RequestHeader>
  </soapenv:Header>
  <soapenv:Body>
    <get xmlns="https://adwords.google.com/api/adwords/rm/v201802">
      <serviceSelector>
        <cm:fields xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802">Id</cm:fields>
        <cm:fields xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802">Name</cm:fields>
        <cm:fields xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802">Status</cm:fields>
        <cm:fields xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802">SizeRange</cm:fields>
        <cm:fields xmlns:cm="https://adwords.google.com/api/adwords/cm/v201802">IsReadOnly</cm:fields>
        <cm:predicates>
          <cm:field>Name</cm:field>
          <cm:operator>EQUALS</cm:operator>
          <cm:values>__some_name__</cm:values>
        </cm:predicates>
        <cm:predicates>
          <cm:field>Status</cm:field>
          <cm:operator>EQUALS</cm:operator>
          <cm:values>OPEN</cm:values>
        </cm:predicates>
        <cm:predicates>
          <cm:field>ListType</cm:field>
          <cm:operator>EQUALS</cm:operator>
          <cm:values>CRM_BASED</cm:values>
          <cm:values>REMARKETING</cm:values>
        </cm:predicates>
      </serviceSelector>
    </get>
  </soapenv:Body>
</soapenv:Envelope>

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.

[alexande...@emarsys.com]

 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

[paradoxx...@gmail.com]

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):

[Sreelakshmi Sasidharan (AdWords API Team)]

Hi All, 

Our team is actively working on fixing this issue. I will keep you posted on the updates.

Thanks,
Sreelakshmi, AdWords API Team

[Sreelakshmi Sasidharan (AdWords API Team)]

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.