Cairn

Slack approval messages failing due to 3000-char block limit

NousResearch/hermes-agent · cluster 53693 · gateway

Data as of

Nothing open on GitHub. Fix merged in #69317. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #69317. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where Slack's chat.update API rejects approval/confirm card updates when section text exceeds 3000 characters, causing the card to never visually update after a button press. Multiple fixes address this by truncating the offending text fields before sending the update.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #69317 fix(slack): sanitize outbound Block Kit payloads — invalid_blocks / msg_too_long hardening

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], plugins/platforms/slack/adapter.py, plugins/platforms/slack/block_kit.py, tests/gateway/test_slack.py, tests/gateway/test_slack_approval_buttons.py, tests/gateway/test_slack_block_kit.py, tests/gateway/test_slack_block_kit_adapter.py

2 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1

  • #53701 fix(slack): truncate inflated original_text in approval/confirm chat.update handlers (#53693) · merged via another change → #69317
  • #62053 fix(slack): truncate section text when updating approval messages · duplicate → #53701, #61697, #43444, #53693, #62054
Closed issues · 2
  • Closed#53693Slack approval/confirm card chat.update fails (invalid_blocks >3000) after button press; approval resolves but card never updates
  • Closed#62054[Bug]: Slack approval UI fails to update when section text exceeds 3000 chars
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: the share of item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Merged PRs
#69317
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
22 Jul 2026

For your agent

The same facts, typed.

cluster/53693.json
cluster/53693.md