How to Fix MongoDB Error 82 (NoProgressMade)
You see mongodb error 82 when the database engine stalls and makes no progress. To fix this NoProgressMade error, clear resource locks, check node health, and retry the operation. Database clusters run many tasks at the same time. Sometimes a background job or a data migration gets stuck in a loop. When the engine sees zero forward movement after several tries, it stops the task. It then returns code 82 so your app does not hang forever. What causes mongodb error 82 in your cluster The offic
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You see mongodb error 82 when the database engine stalls and makes no progress. To fix this NoProgressMade error, clear resource locks, check node health, and retry the operation.
Database clusters run many tasks at the same time. Sometimes a background job or a data migration gets stuck in a loop. When the engine sees zero forward movement after several tries, it stops the task. It then returns code 82 so your app does not hang forever.
What causes mongodb error 82 in your cluster
The official name for mongodb error 82 is NoProgressMade. The database throws this code when a multi-step task cannot move forward. This often happens during chunk moves, index builds, or replica set syncs.
Heavy lock contention is a common root cause in busy clusters. One long write query can hold a lock on a collection for minutes. Other internal tasks wait for that lock to clear. If the lock stays closed across many retry cycles, the waiting task fails with code 82.
Network drops between cluster nodes also trigger this failure. A secondary node might try to pull data batches from a primary node. If packets drop or disk queues fill up, the sync batch makes zero progress. The node aborts the attempt and logs the NoProgressMade code.
Bad client settings can make the problem worse. If an app sends huge bulk writes without breaks, it starves background workers. The database cannot finish its housekeeping work and throws an error.
How to diagnose and fix NoProgressMade safely
Start by checking your database logs and active task lists. Look for long queries that block other work on the same collection. You do not need full admin rights to inspect cluster state.
MongoDB uses role-based rules to control who can do what on each database. A role grants specific actions down to a single collection. For example, the built-in read role lets an engineer run find and stats actions on non-system collections. It blocks insert, update, remove, and drop actions so the user cannot break data during a check.
MongoDB Authentication & Authorization + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Once you find the blocking query or slow disk, you can fix the stall. If a rogue report query holds a lock, ask an operator to stop that task. If disk input and output is at max capacity, slow down your app write rate.
When you need to fix data or rebuild an index, use the readWrite role on that target database. This role adds insert, update, remove, and index actions on top of read access. Avoid granting cluster-wide admin roles to fix a single stalled collection.
How to prevent future stalled tasks
You can stop code 82 from coming back with a few simple habits. Keep your write batches small so background tasks can get locks between writes. Schedule heavy index builds and data moves during low traffic hours.
Set clear timeouts on all client queries. When a slow query stops early, it frees up locks for core cluster work. Also, watch your disk queues and network latency between nodes every day. Fast disks and clean network paths help multi-step tasks finish on the first try.
Finally, review database roles for both people and apps. Give read roles to engineers who only inspect metrics and collection stats. When teams run safe queries and small writes, the engine makes steady progress without stalls.
Inspect MongoDB wire traffic in flight
Built-in MongoDB roles govern collection access at setup time. They cannot score command risk per call or mask sensitive document values on the fly. By design, hoop.dev sits inline in the MongoDB protocol next to your server as a sidecar for your MongoDB. On every production command from mongosh, drivers, or AI agents, hoop.dev decides whether to pass, mask, block, or hold it for human review.
First, hoop.dev guardrails block bad deletes, drops, and write pipelines or hold them for approval. Next, hoop.dev data masking rewrites sensitive values in returned documents in memory and logs each decision. Explore the repo on GitHub.
Frequently asked questions
What does the NoProgressMade message mean in MongoDB?
NoProgressMade is the official name for error code 82 in MongoDB. It means a multi-step internal task tried several times but could not move forward.
Does fixing error 82 require full database admin rights?
No, you can check collection stats and find slow tasks with a basic read role. You only need a readWrite role if you must change data or drop an index.
Can network lag between nodes cause mongodb error 82?
Yes, slow links or dropped packets between replica nodes can stall data syncs. When a node cannot pull any data after many tries, it logs code 82.
Related guides
In this post