Fixed 400 error when author of ticket is no longer an active user in …

[jwjordan]

…a Zendesk account.

Description

In edge cases, there can be Zendesk tickets that have authors that no longer exist in Zendesk. This results in a userId of -1, which then throws a 400 error that is uncaught. I've updated the error handling and the specific cases where -1 is returned.

How Has This Been Tested?

Tested this locally and in a production environment connected to our Zendesk account. The problem ticket was properly processed.

Accepted Risk (provide if relevant)

N/A

Related Issue(s) (provide if relevant)

N/A

Mental Checklist:

• All of the automated tests pass
• All PR comments are addressed and marked resolved
• If there are migrations, they have been rebased to latest main
• If there are new dependencies, they are added to the requirements
• If there are new environment variables, they are added to all of the deployment methods
• If there are new APIs that don't require auth, they are added to PUBLIC_ENDPOINT_SPECS
• Docker images build and basic functionalities work
• Author has done a final read through of the PR right before merge

Backporting (check the box to trigger backport action)

Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.

• This PR should be backported (make sure to check that the backport attempt succeeds)

[vercel]

@jwjordan is attempting to deploy a commit to the Danswer Team on Vercel.

A member of the Team first needs to authorize it.

[yuhongsun96]

lgtm! Thanks for your contribution!