-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
DB Integration & Observability
-
QE 2026-11-23
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The problem: for change streams opted into showErrorsAsEvents, a user stage failing while processing the invalidate event swallowed the invalidate. The client never saw it and never learned the stream had ended — it kept waiting on a silently dead stream (zombie).
The fix: the failure still converts to an error event (errors keep flowing), and the invalidate event is re-delivered right after — so the client sees the stream end and closes cleanly.