Recent searches

No recent searches

Error : 422 Unprocessable Entity

image avatar

Robin

Posted Sep 21, 2022

Hi there

We have an application that is creating a new support ticket.

We have a single user that when they create a new ticket we getting the above response.

```

Uh oh, an error occurred: Client error: `POST https://domain.zendesk.com/api/v2/tickets.json` resulted in a `422 Unprocessable Entity` response: {"error":"RecordInvalid","description":"Record validation errors","details":{"requester":[{"description":"Requester: is (truncated...) [details] {"error":"RecordInvalid","description":"Record validation errors","details":{"requester":[{"description":"Requester: is invalid","error":"InvalidValue"}]}}

```

This is only occurring with a specific user and no other user on the system. It makes me wonder if it's something related to the specific user?

0

8

8 comments

Date
    Newest
      image avatar

      Greg Katechis

      Glad to hear that! Drop us a line if you need anything else!

      0

      image avatar

      Robin

      Thanks for the support here Greg! We changed the ID and all appears to be resolved. Initially I didn't understand the error info received enough to identify the issue. Thanks once again, have a good week!

      1

      image avatar

      Greg Katechis

      Perfect, that was what I was thinking was happening...the merged user no longer existed but was previously hard coded. Hopefully that resolves it, let me know if you run into any more issues though!

      0

      image avatar

      Robin

      Hey Greg, I may have had this resolved on our  side, the specific user in our application has "*7114" saved. So we have changed it to "*5354" and will no test further.

       

      0

      image avatar

      Robin

      Thanks Greg, So the user I'm aware of on our side having an issue ends with "5354"...

      Which I'm referencing from the following URL: https://*.zendesk.com/agent/users/*5354/requested_tickets

      Is this the incorrect way to confirm the ID ?

      0

      image avatar

      Greg Katechis

      Thanks for checking on that! So is the user ID that is being passed in the current ID or is it the previous ID that was merged? For reference, I can see that the ID that we're having an issue with ends in "7114." If that is not the current user ID, then I think we've find where the issue lies!

      0

      image avatar

      Robin

      Hey Greg, thanks for the response and looking into this. From my understanding a merge was done at some point where the user had different emails/ accounts setup and these were consolidated to one. I can supply the user ID of the current account if that isn't sensitive info and it can be of some help?

      0

      image avatar

      Greg Katechis

      Hi Robin! I took a look at your instance and I see the user that you're referring to. I'm also seeing some API calls to the org membership endpoint that is failing with a 422 and 404 when the user lookup occurs. Could you confirm that this user actually exists in your Zendesk instance? Perhaps it did at one point and then was either deleted or merged with another user? Just a thought, if that's not it, we can keep digging into this further.

      0

      Sign in to leave a comment.

      Didn't find what you're looking for?

      New post