# NousResearch/hermes-agent · Google Chat cron messages threading incorrectly as replies

## Open now

- Nothing open on GitHub.

A bug where scheduled cron deliveries in Google Chat appear as replies to the last active thread rather than starting new top-level threads. Two fixes address this by adjusting delivery behavior and skipping a fallback mechanism for cron messages.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #84328. Verify it addresses your case.
- **Recommended:** read PR #84328 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-84328`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #84324: \[Bug\]: Google Chat cron deliveries land as replies in the last active thread instead of a new top-level thread

## Prior & competing PRs

- **#84328: fix(google-chat): post cron deliveries as new top-level threads, not replies**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `plugins/platforms/google_chat/adapter.py`, `tests/gateway/test_google_chat.py`
- **#84338: fix(gateway): skip _last_inbound_thread fallback for cron deliveries in Google Chat**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#84328`

## Fix status

- Merged to main in PR #84328 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-13`.