I have found a couple of similar questions already asked and answered in this forum but the proposed solutions didn't work for me which is why I am creating this new topic.
I have created a data action (an export of data action is attached) which takes interaction id as an input and runs the API call POST /api/v2/conversations/{conversationId}/disconnect. I have tested this using interaction ID 10b2355d-d3e3-49c8-919b-abeec08c7935 and ended up in below error.
{
"message": "You are not authorized to perform the requested action.",
"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 ' conversation:communication:disconnect ' in the provided division(s).","code":"missing.division.permission","status":403} [1db1b133-1c2a-4dfc-b67e-8e31c69bc696]",
"code": "NOT_AUTHORIZED",
"status": 403,
"messageParams": {},
"details": [],
"errors": []
}
]
}
I have verified the user (I am running this data action from) has master admin access and the permission conversation:communication:disconnect is granted for all divisions (snapshot is attached).
The permissions of Genesys Cloud Data Actions actually rely on the Client Credentials that you assigned it in its configuration and not on the user that is running the action.
If possible, please check which OAuth Client Credential is configured for the integration, and provide it the necessary roles.
Thank you. It worked. My data action ran successfully but the excitement was short lived because the interaction in the voicemail queue which I was trying to disconnect is still there waiting to be routed to the agent?
The whole idea (as it was suggested by Genesys Support) was to remove the very old voicemail callback interactions from queue which are there as a back log. Let me share you snapshots.
I have voted for the idea. Now I am wondering how to get rid of this backlog of voicemails waiting to be routed for a callback? I tried using the disconnect tool as well. That too isn't able to disconnect these interactions despite showing the message "Interaction disconnected successfully".
