creating a DISCOVERY ad series through the Google ads API failed。

[余涛]

Hello,

I have encountered an issue where creating a DISCOVERY ad series through the Google ads API failed. What is the problem.

API logs:

Hello,

I have encountered an issue where creating a DISCOVERY ad series through the Google ads API failed. What is the problem.
API logs:
 
2024-05-06 12:00:10.663|-|obd-ad-server|-|grpc-nio-worker-ELG-3-3|-|DEBUG|-|io.grpc.netty.shaded.io.grpc.netty.
NettyClientHandler:214|-||-||-|[id: 0xd842938a, L:/10.86.111.69:58909 - R:googleads.googleapis.com/172.217.25.10:443] OUTBOUND PING: ack=true bytes=707
2024-05-06 12:00:10.669|-|obd-ad-server|-|grpc-default-executor-1|-|WARN|-|com.google.ads.googleads.lib.request.summary:159|-||-||-|FAILURE REQUEST SUMMARY.
Method: google.ads.googleads.v16.services.CampaignService/MutateCampaigns, Endpoint: googleads.googleapis.com:443, CustomerID: 9533424793,
RequestID: JY47_HL-DTPctp63e7i8YQ, ResponseCode: INVALID_ARGUMENT, Fault: Request contains an invalid argument..
 
MethodName: google.ads.googleads.v16.services.CampaignService/MutateCampaigns
Endpoint: googleads.googleapis.com:443
Headers: {developer-token=REDACTED, x-goog-api-client=gl-java/1.8.0_201__Oracle-Corporation gccl/30.0.0 gapic/30.0.0 gax/2.45.0 grpc/1.55.1}
Body: [FAILED toString()]

Response
--------
Headers: Metadata(content-type=application/grpc,request-id=JY47_HL-DTPctp63e7i8YQ,date=Mon, 06 May 2024 04:00:10 GMT,alt-svc=h3=":443"; ma=2592000,h3-29=":443"; ma=2592000)
Body: null
Failure message: [FAILED toString()]
Status: Status{code=INVALID_ARGUMENT, description=Request contains an invalid argument., cause=null}.

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

I see that you have already raised this concern on another thread with the subject "creating a DISCOVERY ad series through the Google ads API failed" and we have already responded there for this issue. To avoid multiple threads on the same issue, please take a look at that thread and continue the discussion on the same for further updates on the issue.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02tIsww:ref" (ADR-00233751)

Thanks,
 

Google Ads API Team