Hi,
Thanks for reaching out to us. I had to delete your initial post as it contained your sensitive Google Ads UI details in the attached screenshots. I am reposting below without the sensitive information for reference :
“Request
Body: customer_id: "***"
operation {
create {
start_time_type: NOW
payments_account: "****"
}
}
Response
--------
Headers:
Body: null
Failure message: errors {
error_code {
internal_error: INTERNAL_ERROR
}
message: "An internal error has occurred."
}
request_id: "******"
Status: Status{code=INTERNAL, description=Internal error encountered., cause=null}. “
Could you elaborate on the issue you're encountering and provide us with the complete request and response logs with the request-id, so our team can better check?
If you are using a client library, you may first enable logging by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link. You may then send the requested information via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.
Regards,
|
||||||
Hi,
Thanks for providing additional details.
Since you were not able to save billing configuration on Ads UI and getting an error, then, I recommend you to reach out to Ads Product team via this link as this is related to saving billing information in UI that is Product related.
With regards to the INTERNAL_ERROR that occurred while using API, so our team can investigate further, could you please provide us with the complete request and response logs as requested before, so that we can check better?
If using the client library and logging is not yet enabled, you may do so by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link.
You may then send the requested information via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.
Regards,
|
||||||