Health and delivery log

The connection dashboard shows a health color, recent delivery outcomes, pending work, and usage counters.

Health colors

• Green — no recent delivery failures are currently affecting the connection.
• Yellow — a recent failure needs attention. Open the delivery log and read the reason attached to the event.
• Red — the connection is paused or repeated failures have made it unhealthy. Fix the destination or Workspace policy, then resume the connection.

Health reflects the app's recent delivery state. It does not guarantee that a human has read the message in Google Chat.

Delivery log

Each connection keeps up to its latest 100 delivery-log entries. Entries include the Jira issue key, event and send timestamps, outcome, Google HTTP status when available, and a short reason. The log is app state in Jira and does not contain the full webhook URL.

Queued digest events appear as queued before a digest is sent. A successful digest records the send outcome for its included events. Older entries are overwritten as new entries arrive.

Retry and recovery

Transient network failures, HTTP 429, and HTTP 5xx responses are retried. If a webhook is missing, invalid, or blocked, correct the connection and use Retry queued where available. Paused connections do not deliver until an administrator resumes them. Queued events expire after 24 hours.

Usage counters

The dashboard shows delivery activity for the app's configured rolling period and first-use milestones. Counters are operational summaries; the Atlassian Marketplace vendor console remains the source for installs, trials, paid subscriptions, and revenue reporting.