# NousResearch/hermes-agent · Discord slash-command sync timeout under rate-limit pressure

## Open now

- Nothing open on GitHub.

All three members concern the Discord slash-command sync timeout (_safe_sync_slash_commands), which has a 30s budget described as too tight after pruning under rate limits. Two pull requests reference #16713 and propose different adjustments: widening the timeout to 600s or scaling it to the number of writes.

## 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 #17029. Verify it addresses your case.
- **Recommended:** read PR #17029 (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-17029`. 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

- #16713: _safe_sync_slash_commands times out under post-prune rate-limit pressure (30s budget too tight)

## Prior & competing PRs

- **#17029: fix(discord): widen slash-sync timeout to 600s under rate-limit pressure (#16713)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/platforms/discord.py`
- **#16739: fix(discord): scale slash sync timeout to actual write count (#16713)**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#17029`

## Fix status

- Merged to main in PR #17029 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-28`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.