What to check when a connected integration, like Slack, Jira, or ClickUp, stops working, from reconnecting an app to reading its error log.
Common causes:
An API key or OAuth connection expired.
The person who created the connection lost API access on the other tool's side.
The destination (a specific Jira project, Slack channel, and so on) was deleted or renamed.
A field mapping no longer matches, often after the other tool's own settings changed.
Start here
Check whether the widget or site itself is paused. A paused site can look identical to a broken integration. Reactivate it before checking anything else.
Check the integration's status on the Connected Apps page. Go to Workspace Settings > Connected Apps and look for a disconnected or errored state.
Read the Integration Log. Go to Workspace Settings > Integration Log, find the relevant call, and open its Log Details panel to see the exact error.
Check the other tool's status page and logs. If Slack, Jira, or another connected tool is having its own outage, reconnecting won't help until that's resolved on their end. Their own activity or audit log may also show an error on their side that isn't visible from Userback.
Reconnect, rename, or delete a connection
On Workspace Settings > Connected Apps, click the ellipsis icon on the app's card. From there you can:
Reconnect, to re-authenticate an expired or errored connection. This reconnects every project tied to that app.
Rename, to relabel the connection for clarity.
Delete, to remove its access entirely.
Read the error in the Integration Log
If reconnecting doesn't fix it, or you're connecting to a tool for the first time and get an error that the connection couldn't be completed, the Integration Log usually has the detail you need.
A 401 or 403 status generally means the connection has lost its authorization and needs reconnecting. Other errors may point to a problem on the other tool's side, in which case you may need to speak with that tool's administrator to resolve it.
Still stuck?
If the steps above don't fix it, email Contact Us with:
The name of the integration
The relevant Integration Log entry, if you have one
Steps to reproduce the issue
Any error shown on the other tool's side
A screenshot of the error, if you have one