Troubleshooting
Check the connection's Delivery log first. The app records a short explanation and, when Google responded, the HTTP status. Never paste a complete incoming webhook URL into a support ticket.
| What you see | Likely cause | What to do |
|---|---|---|
| “Paste the complete incoming webhook URL from Google Chat.” | The value is empty or is not a URL. | In the Chat space, create or copy an incoming webhook URL and paste the complete value. |
| “Use a Google Chat incoming webhook URL with a space, key, and token.” | The URL host, path, or required query parameters do not match a Google Chat webhook. | Create a new incoming webhook in the target space and replace the saved destination. |
| HTTP 400 | Google Chat rejected the request, the webhook is not current, or the message format was rejected. | Create a fresh webhook and use the app's Test action. If it persists, contact support with the time and HTTP status, never the URL. |
| HTTP 403 | Workspace policy or permissions block incoming webhooks. | Ask a Workspace administrator to allow incoming webhooks for the applicable user or organizational unit. Then test again. |
| HTTP 404 | The webhook or space no longer exists, or the webhook was revoked. | Create a new webhook in the intended space and update the connection. |
| HTTP 429 | Google Chat is rate limiting traffic to the space. | The app retries automatically. Reduce other webhook traffic and allow the queue to drain. |
| HTTP 5xx | Google Chat is temporarily unavailable. | The app retries automatically. Check the delivery log later and retry any queued items still eligible. |
| Network or timeout error | The app could not reach the destination or the request timed out. | Check Atlassian Forge and Workspace status, verify the webhook is current, and retry. |
| No message and no delivery entry | The issue may not match the rule, may have a security level, the connection may be paused, or the event may not have reached the app. | Preview the rule, check the project/JQL and event types, confirm the issue is not restricted, and inspect the connection state. |
| “Connection paused” | An administrator paused the connection or the app paused it after repeated failures. | Correct the underlying destination or policy, then resume and retry queued events. |
The exact wording can vary by app version. The HTTP mappings above reflect the current app's friendly-error mapping. See also Google's incoming webhook guide.