HomeBrandsMongoDBDatabase Server & Atlas142
M
142
Call a Pro
MongoDB · Database Server & Atlas
MongoDB server reported: Incomplete Transaction History.
Quick Answer
Error code 142 on your MongoDB Database Server & Atlas means: MongoDB server reported: Incomplete Transaction History.. This is usually fixable — see the step-by-step guide below.
Affected Models
Applies to all models
MONGO-ATLAS-DEDICATEDMONGO-ATLAS-SERVERLESSMONGO-COMM-6.0MONGO-COMM-7.0MONGO-COMM-8.0MONGO-ENT-6.0MONGO-ENT-7.0MONGO-ENT-8.0
Likely Causes
  1. MongoDB returned code 142 (IncompleteTransactionHistory) while processing this request path.
  2. Transaction coordinator state changed, forcing retry or rollback logic.
  3. Transaction/session lifecycle moved to a conflicting state before completion.
How to Fix It
1
Review logs/telemetry for code 142 (IncompleteTransactionHistory) and capture the exact command and parameters that triggered it.
2
Retry the whole transaction flow (not partial fragments) with idempotent boundaries.
3
Review coordinator logs to distinguish retriable aborts from terminal state conflicts.
4
Load full transaction/session trace to identify the exact conflicting transition.
5
Add monitoring for recurring IncompleteTransactionHistory events so future incidents are detected and triaged faster.
Pro Tip
This issue typically requires professional diagnosis. Attempting this fix without proper training could cause further problems.
Related Error Codes
12456
Video Guides
Loading video guides…
Search more on YouTube →