Get Estimated Wait Time Data Action

[Chase_Hamby]

Hi all,

I am trying to use the static Estimated Wait Time data action from the PureCloud Data Actions integration in our webchat 2.0 widget. When I go to test and input the queue ID, it returns a 403 permissions error (see below). Most of my roles have the routing:queue:view permission selected. Is there a particular role or something else that I'm missing? Our credentials are configured with the integration.

Thanks in advance!

{
  "message": "You are not authorized to perform the requested action.",
  "code": "not.authorized",
  "status": 403,
  "messageParams": {},
  "contextId": "0c2477b8-1d03-44ad-a944-e5c26b6f4f04",
  "details": [
    {
      "errorCode": "ACTION.REMOTE_ENDPOINT"
    }
  ],
  "errors": [
    {
      "message": "REST call for action execute failed. Message:Request to backend service failed.  Response from web service: {\"message\":\"Unable to perform the requested action. You are missing the following permission(s): [routing:queue:view:f985995c-dbb9-44a6-8729-f15f421e7e15]\",\"code\":\"missing.permissions\",\"status\":403} [0c2477b8-1d03-44ad-a944-e5c26b6f4f04]",
      "code": "NOT_AUTHORIZED",
      "status": 403,
      "messageParams": {},
      "details": [],
      "errors": []
    }
  ]
}

[tim.smith]

This error means that the user making the request does not have the permission routing:queue:view:f985995c-dbb9-44a6-8729-f15f421e7e15. Check to be sure that the user has a role assigned that grants this permission for the appropriate queues/divisions.

[Chase_Hamby]

Thanks Tim,

I've tried testing it myself and I have several roles assigned to me that grant this permission and I'm still getting this error message.

[tim.smith]

Please open a case with Genesys Cloud Care to investigate further.

[Chase_Hamby]

Thanks! Will do.

[Jason_Mathison]

I see a couple of comments in this thread talking about user permissions, which could be the root of your issue. The Data Action gets it's permissions based on the client credential it is configured to use no matter what user executes the data action. Make sure that the client credential in adimin->integrations->OAuth -> {credential used by the data action} -> Roles includes a role that has the needed permission.

--Jason