cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
946
Views
0
Helpful
4
Replies

Unable to get attachment action details

HarryPickthall
Level 1
Level 1

Hi, I have api calls going to get attachment action details. Most of these go through fine but some come back as 404 Unable to get attachment action. I'm struggling to find why, I'm confident the data is being submitted by users. Any help appreciated!

1 Accepted Solution

Thanks for sharing this. Checking the logs, I found an error that states the following: "Action ID can be read only by the author of the original card activity or cardAction author".

It looks like the bot that made the request to GET attachmentAction is csmbot@webex.bot, did this bot create the card?

If yes, please create a ticket with us at devsupport@webex.com so that we can check on it further. Please share the card JSON and also share the tracking ID of the POST to /messages API that you sent to create this card (and the JSON request for that too, if you have it). Tracking ID can be found in the Response Headers.

View solution in original post

4 Replies 4

HarryPickthall
Level 1
Level 1
{
  "message": "Unable to get attachment action.",
  "errors": [
    {
      "description": "Unable to get attachment action."
    }
  ],
  "trackingId": "WEBEX-DEV-PORTAL_e44c6731-78cf-4150-a1b9-90f5e64dd69d_2"
}

In terms of reproducing, I'm struggling to as I can't find a pattern to which calls are returning 404. We have a few different adaptive cards that go out and it seems to happen at random across them. Certainly if an ID returns 404 it seems to always return 404

Thanks for sharing this. Checking the logs, I found an error that states the following: "Action ID can be read only by the author of the original card activity or cardAction author".

It looks like the bot that made the request to GET attachmentAction is csmbot@webex.bot, did this bot create the card?

If yes, please create a ticket with us at devsupport@webex.com so that we can check on it further. Please share the card JSON and also share the tracking ID of the POST to /messages API that you sent to create this card (and the JSON request for that too, if you have it). Tracking ID can be found in the Response Headers.

Looks like that was the problem! Thanks for your help

Raffaele Lagana
Cisco Employee
Cisco Employee

Can you share the error response you got, as well as how you're reproducing the error?