Hi Felipe,
I think I already figured out the problem with my production environment.
My production run a cron job to get all devices’ information periodically via NBI and this is the main cause of the exceptionName=“Error” exceptionMessage=“Database clock skew too great” and exceptionName=“MongoNotConnectedError” exceptionMessage=“MongoClient must be connected to perform this operation”. So, mongoDB high load is the main cause of this problem.
I just add some delay and reduce the number of devices / each request from my cron job and now problem disappeared.
For others: please check the mongoDB read/write statistics (using Studio3T) when problem happen and identify the source of problem in your environment.