-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Could the Node.js driver expose a supported isConnectionError(err) helper? We're classifying Atlas Remote MCP failures as expected vs. alertable, and maintaining our own list of driver error types is brittle. It'd be useful if it covered network error subclasses, SRV/TXT DNS failures, and the underlying causes in MongoServerSelectionError.
Context: Slack thread