Backend error when creating placements

[maranz....@gmail.com]

Hi team,

I am testing multiple placement of type diplay (mostly for HTML / JPG assets) creation from java application using DCM API, and I am having some issues.

Attempting to parallelize API calls I got the following response:

{

  "code" : 503,

  "errors" : [ {

    "domain" : "global",

    "message" : "915 : We can't process your request at this time. Please try again later.",

    "reason" : "backendError"

  } ],

  "message" : "915 : We can't process your request at this time. Please try again later."

}

As there is a QPS limit, I was expecting to get some type of "limitExceeded" error, not this one. More over, these tests were performed with just six placements in the first go (two were successfully created, four got this error) and repeated with the remaining four ones (one was created, three got this error)... and I wasn't expecting to get any kind of error with so few objects, to be fair.

So the first question is: Is there any type of incident active right now? and if not, why I am getting a "backend error"?

Also, on another test in which I created three placements and assigned one different ad to each of these, I found one of them had no default ad assigned; on the change log that one it showed that the default ad was assigned and immediately after removed. I got no errors with the calls, objects and assignments were successfully performed... but the default ad assignment was missing in that placement. 

As assigning the default ad is done silently by DCM once I create the placement, this raises the question: why would DCM be removing it?

Let me know if you need more specific information.

Thanks in advance for your help.

Regards,

Miguel Angel

[maranz....@gmail.com]

Hi,

Some update. I have tested that the same placements do not provide an error if created sequentially (awaiting DCM response instead of attempting several requests in parallel).

Also, placements of type "Tracking" or "Dynamick Click Tracker" do not have issues even if created in parallel. Only placements of type "Display" seem to have an issue. (I have NOT tested more types, these are the ones we usually use).

Also, once all placements are successfully created, creating ads and assigning them seems to not have any issue even if perfomed in parallel.

So, could yoy provide some insight about why Display placements are throwing this backend error when attempting to create them simultaneously? (and how to avoid it, if possible)

Thanks in advance.

Regards,

Miguel Angel

[DCM API (DoubleClick Campaign Mgr)]

Hi Miguel,

Please provide the following details using reply privately to author option:

1. Sample API request in JSON format
2. DCM account id
3. Profile id
4. Timestamp of the failed API request
5. Google Console Project id

The reply to author option is only visible to group members. If you don't see that option, please join the group.

Thanks,
Lakshmi, DCM API Team

 

ref:_00D1U1174p._5004Q23tawi:ref

[Nirmit Bothra]

Were you able to get a solution for the removal of placements from default ads? We are running into a similar issue but its intermittent.. only a few placements get attached and then instantly removed from the default ad group.

[DCM API (DoubleClick Campaign Mgr)]

Hello Nirmit,

 

Michael here from DCM API support team. Thank you for reaching out to us.

 

As this original forum thread seems to be old, would it be possible for you to create or post a new forum thread with the details of your issue? Asking this for better tracking of issues as shared information here may not be relevant anymore due to the time that had already passed. If that cannot work for you, then we can continue on this thread instead.

 

Would you be able to confirm where did you encounter the issue? Is it from creating through API or UI side? As you mentioned that this is intermittent, when did you start seeing the issue and can you give us ratio of how frequent this happens?

Regards,

Michael Angelo DCM API Team

ref:_00D1U1174p._5004Q23tawi:ref