ConnectWise — Troubleshooting

Troubleshoot common ConnectWise integration errors with likely meanings and recommended next steps.

📘

Related setup guide

Setting up ConnectWise? See the ConnectWise integration setup guide.

Use this page to troubleshoot common ConnectWise integration errors, understand what each error usually means, and choose the next action.

Error messageLikely meaningRecommended next steps
"code": "MaxLengthField"
"message": "The field summary must be a string with a maximum length of 100."
The ticket summary is too long. ConnectWise allows a maximum of 100 characters.Shorten the ticket title or summary, then try again. Put longer details in the ticket description instead of the title.
Query read timeoutThe ConnectWise database timed out while processing a large or slow request.Try again later. If the issue continues, contact Support with the Integration ID and the time the error occurred.
"code":"Security"
"message":"You do not have security permission to perform this action."
The ConnectWise API member does not have permission to read ticket statuses for the relevant Service Board.Ask your ConnectWise admin to grant the integration user the required Service Desk security rights for that board, or use an API member with sufficient permissions. Then retry the request.
"message": "Incorrect public/private key"The public/private API key pair is incorrect or does not match the ConnectWise API member.Verify the public and private keys for the ConnectWise API member. If needed, generate a new key pair and reconnect the integration.
Failed to get User Profile. Check your account details and try again.
"output": "Invalid Token"
The saved token or API member credentials are invalid.Check that the member API keys are populated correctly. If needed, create a new key pair and reconnect the integration.
ConnectWise: Error: "code": "InvalidObject", "message": "ticket object is invalid"
"message": "Service Status 17 not found for Service Board 21"
The selected ticket status does not exist on the target Service Board.Choose a valid status for that Service Board. Ask your ConnectWise admin to confirm the correct board and status mapping.
Connect SDK attempted to make an API request, but no user was authenticated.The SDK request was made before a user was authenticated.Refresh the browser and retry the action.
"message": "Your authorization token has expired."
"code": "7203"
"status": 401
The authorization token expired or the connection details are no longer valid.Check the company ID/name and reconnect the integration if needed.
An unexpected database error has occurred.ConnectWise returned a temporary database error.Try again later. If the issue continues, report it to your ConnectWise admin with the time it occurred and the Integration ID.
"message": "Status cannot be updated on a merged ticket."The ticket was merged into another ticket, so its status can no longer be updated directly.Update the main ticket that the original ticket was merged into. If ticket merging is expected in your process, treat this message as informational.
"message": "The set of specified public/private keys have been inactivated."The ConnectWise public/private keys were disabled.Ask your ConnectWise admin to generate new keys and update the integration. After updating the keys, reconnect the integration.
"Cannot read properties of null (reading 'length')"The request contains an empty or unexpected field, causing a server-side error.Reconnect the integration and try again. If the issue repeats, share the Integration ID and Paragon request ID with Support or your admin so they can identify the problematic field.
"Unable to validate/refresh the connect credentials. Please check the credentials and try reconnecting."The saved connection expired or the credentials can no longer be refreshed.Reconnect the Paragon integration. If the credentials were changed or rotated, reconnect using the updated credentials.
Workflow has been enqueued but has not completedThe workflow was queued but has not finished running yet.Wait for the workflow to complete, then check the result again. If it remains stuck, contact Support with the Integration ID.
New State "ABCD" not found on ConnectWise - please re-check configurationThe configured state does not exist in ConnectWise.Review the ConnectWise configuration and choose a valid state. Then retry the sync or workflow.
"message": "Failed to get User Profile. Check your account details and try again.", "code": "0704", "status": 400, "apiError": "message": "Request failed with status code 403", "statusText": "Forbidden", "output": "code": "Security", "message": "You do not have security permission to perform this action."ConnectWise rejected the user-profile validation request because the API member does not have the required security permissions. The credentials may be valid, but the API member’s Security Role is missing access to the required ConnectWise resource/action.Ask the ConnectWise admin to check the API Member’s Security Role and grant the required permissions. Then reconnect or retry the integration. If the issue continues, verify the Company ID, public/private keys, and that the API member is active.
Failed to open TCP connection to api.useparagon.com:443 (execution expired)The connection to the ConnectWise integration service (Paragon) timed out, so the request could not be delivered. This is usually a temporary network or service issue.Wait a few minutes and retry — this is often transient. If it persists, check the integration service status and reconnect the ConnectWise integration.
"code": "NotFound"
"message": "Ticket <ticket ID> not found"
The ConnectWise ticket linked to a Xyte incident was deleted in ConnectWise. When the incident closed, Xyte couldn't close that ticket. After a few retries, the integration went into error. While it's in error, no incidents are sent to ConnectWise.Re-enable the integration: Integrations → ConnectWise → enable. The deleted ticket won't cause this error again. Incidents opened or closed while the integration was in error weren't sent, so check those tickets in ConnectWise. To avoid this, close tickets in ConnectWise instead of deleting them while the Xyte incident is still open.

When the integration stops creating tickets

If Xyte can't create or close a ticket in ConnectWise, it tries again after 1 minute, then 5, then 15 (about 20 minutes in all). A few errors, such as a Region address that isn't valid or can't be resolved, skip the retries. If the last try also fails, the integration switches to Error.

📘

Spaces with their own ConnectWise company

If a space sends its tickets to its own ConnectWise company (the space's Settings → Incidents → Routing) and ConnectWise refuses to create a ticket for that company, Xyte retries and records the failure, but the integration does not switch to Error. Other failures for that space, such as wrong API keys, rate limits, timeouts or ConnectWise server errors, are handled like any other ticket.

While the integration is in Error:

  • It stops creating and closing ConnectWise tickets for the whole organization, not only for the incident that failed.
  • Tickets for incidents raised while it's off aren't created later, even after you turn the integration back on. Check those incidents in Xyte and open tickets for them by hand if you need them.
  • Incidents that were resolved while it was off leave their ConnectWise tickets open. Close those tickets by hand.
  • The organization's admin contact (Settings → Contacts) gets an email about it.

Where to see it: on the Connections → Integrations page, the ConnectWise row shows a red Error badge. Hover over the badge to see the error message. When ConnectWise answered, the message includes the HTTP code and ConnectWise's reply. The line under the row shows Failing since with the date and time the integration switched to Error. If your portal doesn't have an Integrations page, go to Settings → Integrations → Ticketing System → ConnectWise; the error message appears in red under the setup steps.

How to turn it back on: a user with admin rights in the organization clicks Fix on the ConnectWise row (or opens Settings → Integrations → Ticketing System → ConnectWise), goes to the Enable step and clicks Activate. If the service board the integration used was deleted in ConnectWise, first pick a new board in the Board step, then the New ticket status and Closed ticket status in the Statuses step, and then activate in the Enable step.

Board and status changes in ConnectWise: renaming the service board or a status is safe. Xyte keeps the board and statuses by their ID, not their name. If you delete the service board or a status the integration uses in ConnectWise, open the setup steps, pick the new board and/or statuses, then click Activate in the Enable step.


Did this page help you?