Bug: Feishu dedup cache lost on gateway restart causes message replay
Bug: Feishu dedup cache lost on gateway restart causes message replay
When the gateway restarts, the in-memory dedup cache () is cleared. Feishu's WebSocket then redelivers recent messages on reconnect, and since the message IDs are no longer in cache, they get processed again as new messages.
Steps to reproduce:
1. Send a message via Feishu
2. Restart the gateway
3. The same message is processed again
Root cause: is a plain in-memory with 30min TTL โ not persisted to disk. Any restart wipes it.
Suggested fix: Persist processed message IDs to a file (e.g. ) and reload on startup, keeping only entries within the TTL window.
When the gateway restarts, the in-memory dedup cache () is cleared. Feishu's WebSocket then redelivers recent messages on reconnect, and since the message IDs are no longer in cache, they get processed again as new messages.
Steps to reproduce:
1. Send a message via Feishu
2. Restart the gateway
3. The same message is processed again
Root cause: is a plain in-memory with 30min TTL โ not persisted to disk. Any restart wipes it.
Suggested fix: Persist processed message IDs to a file (e.g. ) and reload on startup, keeping only entries within the TTL window.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
