Threads, quiet hours, and digests

Threads

Immediate updates about one Jira issue use a stable issue thread key. This groups later updates for that issue together when the Google Chat space supports threaded webhook messages. Different issues use different thread keys. Digest cards are sent as digest messages rather than one message per issue thread.

Delivery timing

Choose a timing mode for each connection:

• Immediately — send each matching event as it is processed.
• Hourly digest — collect matching events and make a digest due once the first queued event is at least one hour old.
• Daily digest — collect events for the selected daily delivery time in the connection's IANA timezone.
• Quiet hours — hold messages during the configured local-time interval and release them after quiet hours end.

Forge checks scheduled digests every five minutes. A message may therefore be released after the next scheduled check rather than at the exact minute. Google Chat rate limiting and temporary platform delays can add time.

Digest size and retries

Digest cards contain up to 20 issue updates. Larger batches are split into additional cards. After one card is delivered, remaining cards are placed back on the queue for continued delivery while preserving the per-space rate limit.

Temporary network failures, HTTP 429 responses, and Google Chat HTTP 5xx responses are retried. Events that cannot be delivered remain queued for up to 24 hours. The app uses idempotency markers to reduce duplicate processing.

For delivery state, see Health and delivery log. For Workspace permission issues, see Troubleshooting.