card-callback-performance

Card callback timeout error 200340 occurs when card interactions exceed the 3-second response limit on IM platforms. Expensive I/O operations like ListSessions, file scanning, or JSONL parsing in the callback path block rendering and trigger this timeout.

To keep Feishu card interactions under 3 seconds, implement a deterministic caching pattern with a 30-second TTL for expensive data like ListSessions. This prevents blocking I/O during card callbacks such as page turns and checkbox toggles.

The best way to cache session lists for IM cards is using a TTL-based cache with a 30-second expiration. This approach ensures list rendering data is served quickly while providing explicit invalidation hooks when mutations occur.

You need to invalidate the session list cache when mutations occur, such as data modifications from card interactions. Explicit invalidation clears the 30-second TTL cache, ensuring the next card render fetches fresh data without causing timeouts.

No, you should use separate paths for card callbacks versus slash commands. Card callbacks enforce a strict 3-second timeout for rendering interactions, requiring a 30-second TTL cache, while slash commands can handle I/O differently.