Legacy Dev Forum Posts

 View Only

Sign Up

Error on api/v2/conversations/{conversationId}/assign

  • 1.  Error on api/v2/conversations/{conversationId}/assign

    Posted 06-05-2025 18:20

    mgalindo | 2021-09-03 14:58:43 UTC | #1

    Hi, im using this request to assign manualy interactions to agents, but sometimes (most of times) i get this error

    "body":{"message":"Conversation fd3a6365-dea4-4b40-b845-8be9bfbff118 is pending assignment to agent 548053f0-7151-4fc4-9c12-210cd14b91ac","code":"operation.failed","status":400,"messageWithParams":"Conversation fd3a6365-dea4-4b40-b845-8be9bfbff118 is pending assignment to agent 548053f0-7151-4fc4-9c12-210cd14b91ac","messageParams":{},"contextId":"002145d8-a77e-47a8-a863-6190018df0bf","details":[],"errors":[]}

    i want to understand exactly where this needs to be invoked! thanks!


    Jerome.Saint-Marc | 2021-09-06 07:34:19 UTC | #2

    Hello,

    I think this error is sent back when you are trying to assign a conversation to an agent (e.g. Agent1) and that the conversation you are trying to assign is already alerting another agent (e.g. Agent2 has received the interaction - "in ringing/alerting" state). I assume that "548053f0-7151-4fc4-9c12-210cd14b91ac" should correspond to the id of Agent2 (the one who is being already alerted by this conversation).

    Regards,


    mgalindo | 2021-09-08 13:50:37 UTC | #3

    Hi Jerome thanks for taking the time to answer me, you are correct in everything, so i will have to "catch" the interaction an event before the ring and try to asign the interaction there, thank you i will do it!


    system | 2021-10-09 13:51:19 UTC | #4

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 11913