No way to avoid ReplicaSetNoPrimary errors

[Kushagra_Kesav]

Hey @Pyra_Metrik,

@Pyra_Metrik

Is there any way we can verify that the ReplicaSetNoPrimary errors are indeed from network failures, by checking logs somewhere (or something else)?

1. Just to clarify, have you reached the Atlas in-app chat support team for any notable cluster issues during the time these errors occurred?
2. May I ask if you notice any patterns in the timing of these errors?
3. Also, could you please provide specific information like the connection string (with sensitive credentials redacted) and details about the client-side environment (e.g., containerized, Lambda, etc.).

The above details will help us to assist you better.

Regards,
Kushagra