Reference
Troubleshooting
Each connected channel shows how many messages were sent and the last error. Start there.
The channel cannot be saved
“This is not a Zoom incoming-webhook endpoint”
Paste the endpoint that /inc connect showed in the channel; it starts with https://integrations.zoom.us/chat/webhooks/incomingwebhook/.
“Paste the verification token that /inc connect shows next to the endpoint”
The token field is empty or contains more than the token. Copy only the token from Zoom's reply.
The test message does not arrive
“Zoom refused the webhook (401/403/404)”
The connection was removed in Zoom, or the token changed. Run /inc connect jira in the channel again, then Edit the channel in Chatline and paste the new endpoint and token.
“Zoom is busy (429)” or “Zoom could not be reached”
Too many messages at once, or Zoom had an outage. Chatline retries automatically; nothing to do.
The Incoming Webhook app cannot be added
Your Zoom account admin may have to approve apps from the Zoom App Marketplace. Ask them to allow Incoming Webhook.
The test works, but changes are not posted
- Is the channel On, and is the kind of change ticked under Post when?
- Does the issue match the JQL filter? Run the filter in Jira issue search.
- Does the issue have a security level? Those are skipped while Skip issues that have a security level is on.
- Was the change made by an automation rule while Ignore changes made by apps and automation rules is on?
- Is the comment restricted to a role or group, or an internal JSM note? Those are never posted.
- Is the license of the site active? A notice at the top of the settings page says so if not.
The time reminder posts nothing
Nothing is posted when everyone logged at least the expected hours. Click Check logged time now on the channel: it shows how many people were checked and how many logged too little.
Messages arrive late or out of order
Zoom limits how many messages an incoming webhook accepts in a short time. During bursts Chatline queues the rest and retries for up to about 15 minutes, which can change the order slightly.
Still stuck?
Write to support@yti.digital with the channel name and the error shown on the settings page. Do not send the endpoint and verification token.