AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED error since 2018-04-12 on /api/adwords/ch/v201802/CustomerSyncService

[Adwords account]

Hi,

 

We experiencing issues when calling /api/adwords/ch/v201802/CustomerSyncService service since around 2018-04-12 02:00:00 EET. Although AdWords API team states that these errors should be fixed now, our calls are still failing. When appropriate actions will be taken to mitigate the issue?

Failed reguest logged:
 

<?xml version="1.0" encoding="utf-16"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

  <soap:Header>

    <ns2:ResponseHeader xmlns:ns2="https://adwords.google.com/api/adwords/ch/v201802" xmlns="https://adwords.google.com/api/adwords/cm/v201802">

      <requestId>_RequestID_</requestId>

      <serviceName>CustomerSyncService</serviceName>

      <methodName>get</methodName>

      <operations>1</operations>

      <responseTime>142</responseTime>

    </ns2:ResponseHeader>

  </soap:Header>

  <soap:Body>

    <soap:Fault>

      <faultcode>soap:Server</faultcode>

      <faultstring>[AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED @ ; trigger:'&lt;null&gt;']</faultstring>

      <detail>

        <ns2:ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201802" xmlns:ns2="https://adwords.google.com/api/adwords/ch/v201802">

          <message>[AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED @ ; trigger:'&lt;null&gt;']</message>

          <ApplicationException.Type>ApiException</ApplicationException.Type>

          <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AuthenticationError">

            <fieldPath></fieldPath>

            <trigger>&lt;null&gt;</trigger>

            <errorString>AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED</errorString>

            <ApiError.Type>AuthenticationError</ApiError.Type>

            <reason>CLIENT_CUSTOMER_ID_IS_REQUIRED</reason>

          </errors>

        </ns2:ApiExceptionFault>

      </detail>

    </soap:Fault>

  </soap:Body>

</soap:Envelope>

[Luis Xander Talag (AdWords API Team)]

Hi,

There was a recent issue that was reported to our team regarding this. However, we've received information that the issue has now been resolved. Could you retry your requests and check if you still encountered the error on your end? If so, could you provide the latest SOAP request and response logs when the error occurs? Please reply via Reply privately to author.

Thanks and regards,

Luis

AdWords API Team

[Michael Cloonan (AdWords API Team)]

Hello,

We have gotten another report of this same issue, so I've escalated for our team to take a look. I will let you know as soon as I have more information to share.

Regards,

Mike, AdWords API Team

[vygint...@adform.com]

Hi,

Any updates on this one?

BR,

Vygintas

[Michael Cloonan (AdWords API Team)]

Hello,

Not yet. I will keep this thread posted with new information as it is available.

Regards,

Mike, AdWords API Team

[vygint...@adform.com]

Hi,

Do you have the ETA for this? We applied a temporary workaround, but this situation is getting a bit annoying.

Ragards,

Vygintas

[Michael Cloonan (AdWords API Team)]

Hello,

We have identified the cause of this and are in the process of rolling out a fix. I would expect it to be live sometime early next week, but I will post again here when I confirm that it is rolled out.

Regards,

Mike, AdWords API Team

[Michael Cloonan (AdWords API Team)]

Hello,

I apologize for the delay. I just wanted to follow up to say that this fix has been rolled out and you should no longer be encountering this error. Please let me know if you still so we can take another look if necessary.

Regards,

Mike, AdWords API Team