Message
Connection to xxxxxxxx.mongodb.net:27017 interrupted due to server monitor timeout.
Cause
The database server that the service running this flow was connected to was restarted due to the monitoring process not getting a response from the server within the time limit. This causes an interruption in server connectivity. This can happen for several reasons including:
MongoDB maintenance
Cloud provider issues or downtime
Server CPU / memory problems caused by highly non-performant queries
Extremely high server load
Resolution
Depending on the cause of the interruption, there are no direct steps to take to resolve this error. After a brief moment, the database server will restart, connectivity will resume, and the failing flow should execute without this error.
In terms of prevention of this error, the only steps that one can take are to make sure that all queries performed are optimized to be as lean as possible, and that they are always supported by a Buffer index.
Error Detail
{
"error": {
"address": "xxxxxxxxxxxxxxx.mongodb.net:27017",
"statusCode": 500,
"commandProcessingError": null,
"name": "PoolClearedOnNetworkError",
"message": "Connection to xxxxxxxxxxx.mongodb.net:27017 interrupted due to server monitor timeout"
}
}