Slack now recovers missed messages in mapped channels, recent threads and channels relayed from another machine. Reported by a community member.
Slack recovers what it missed in more places. Missed-message recovery used to read only the configured channel's top-level history, so a reply in an older thread or a message in a mapped channel was lost for good. It now also recovers the channel map's channels from when each was adopted, replies in tracked threads whose root was posted or which closed in the last seven days, and, on a machine without its own Socket Mode connection, each channel the hub has relayed to it, from that channel's first relayed event. A recovered reply lands as a late row in its thread and never answers a decision; the seat reads it and decides. A Slack rate limit now holds that method for every channel, or every thread, and is kept across a restart. rig slack status shows a line per channel and a thread line. On its first start, threads inside the seven-day window are scanned once from their root; replies that already landed are recognised and not delivered twice.
Missed replies in older open threads aren't caught up; `slack-thread-coverage.json` isn't pruned yet; a default-channel backlog can drain at up to about half its earlier rate while threads also need calls; and a downgrade to an older release and back inside a rate-limit window can let other channels call Slack during that window.
- Pull request
- #1536
- Reported by
- @z4cc
- Release
- OpenRig 0.6.13 release notes