Adding a User to Queue results in a 500

Platform API
1

Using the Developer Tools, I was able to add a user to a Queue with a POST to:

/api/v2/routing/queues/{QueueId}/users

With this body:

[{"id": "db910720-0658-4ef4-93a1-69bab940fd6d"}]

When I change to this body, a newly created user through the API:

[{"id": "61162b3d-6870-41b3-a6ec-9192264d6024"}]

I get a 500 back. Correlation Id: 821d2241-da20-4f8a-94be-e26fba93a382

Does this have to do with the user being brand new and having no Roles assigned yet?

2

I tried re-ordering, and adding Roles first doesn't help. I can add the User, Roles, and Skills all fine through the API. As soon as I get to add the user to a Queue, it fails. It only seems to do this with a user I created with the API.

3

I'm seeing an error from a backend service with the message "Expected an int but was 0.5 at path $[0].skills[0].proficiency". Have you set a routing skill with value 0.5 somewhere? I see that the API docs say "from 0.0 to 5.0" for proficiency, but I believe that's a formatting error and should be an integer.

4

Yes, that's exactly what I did. If that's an int and not a number, let me make a change and try again.

Thanks!

5

Where exactly did you provide the 0.5 value? Was it POST /api/v2/users/{userId}/routingskills? I'd like to get a bug filed for the API resource to throw an error for invalid values.

6

Yep, that's the one.

I just tested again with an int, and it's working correctly.

Thanks!

1 Like
7

Thanks for confirming. I've opened AS-886 to put a check on that property and update the docs to reflect the correct valid values.

8