Sandbox problem deleting campaign

bug
sandbox
api

#1

Dear Twitter staff.
We are experimenting issues when we try to delete a campaign, we are having a 500 error.
We have no problem listing the account campaigns, but we have issues creating new campaigns, updating campaigns and/oir deleting campaigns, all this on the sandbox.

Please see the following twurl with the full trace:

twurl -t -X DELETE -H ads-api-sandbox.twitter.com "/0/accounts/gq10iy/campaigns/g9se" | jsonpretty
<- ""
-> "HTTP/1.1 500 Internal Server Error\r\n"
-> "connection: close\r\n"
-> "content-disposition: attachment; filename=json.json\r\n"
-> "content-encoding: gzip\r\n"
-> "content-length: 109\r\n"
-> "content-type: application/json;charset=utf-8\r\n"
-> "date: Mon, 28 Mar 2016 18:35:06 GMT\r\n"
-> "server: tsa_b\r\n"
-> "set-cookie: guest_id=v1%3A145919010652386565; Domain=.twitter.com; Path=/; Expires=Wed, 28-Mar-2018 18:35:06 UTC\r\n"
-> "strict-transport-security: max-age=631138519\r\n"
-> "x-access-level: read-write\r\n"
-> "x-connection-hash: b027307e93de6809e7ed5c6243049bab\r\n"
-> "x-content-type-options: nosniff\r\n"
-> "x-frame-options: SAMEORIGIN\r\n"
-> "x-rate-limit-limit: 300\r\n"
-> "x-rate-limit-remaining: 300\r\n"
-> "x-rate-limit-reset: 1459190166\r\n"
-> "x-response-time: 249\r\n"
-> "x-runtime: 0.076906\r\n"
-> "x-transaction: 8f21b172260f4c62\r\n"
-> "x-xss-protection: 1; mode=block\r\n"
-> "\r\n"
reading 109 bytes...
-> ""
-> "\x1F\x8B\b\x00\x00\x00\x00\x00\x00\x00\xAAVJ-*\xCA/*V\xB2\x8A\xAEVJ\xCEOIU\xB2R\xF2\xF4\vq\r\xF2s\xF4\x89w\r\n\xF2\x0FR\xD2Q\xCAM-.NL\aK\xE5\x95\xA4\x16\xE5%\xE6(\xB8\x82t)\xD5\xC6\xEA(\x15\xA5\x16\x96\xA6\x16\x97(YU+\x15$\x16%\xE6\x02\x8D\xAA\xAE\xAD\xAD\x05\x00\x00\x00\xFF\xFF\x03\x00\x14\xCE\xF7\xFEY\x00\x00\x00"
read 109 bytes
Conn close

Here is the response

{
  "errors": [
    {
      "code": "INTERNAL_ERROR",
      "message": "Internal Error"
    }
  ],
  "request": {
    "params": {
    }
  }
}

#2

Thanks for reporting this bug in the sandbox, we’re looking into it.


#3

Thanks for reporting this bug. We’ve identified the cause and the DELETE functionality should be restored.