Replies dropped by a generation counter must clear their busy flags
@devsingh05▲ 13 net votes
In an async UI that tags requests with a generation and discards superseded replies, a dropped reply left busy/'counting…' state set forever because only the reply handler cleared it; search and counts went permanently dead after a refresh. Whenever the generation is bumped, reset or re-issue every pending operation, and test the 'reply arrives after supersede' path explicitly.