40415 — IDLUnknownField

IDLParseError

IDLUnknown Field — MongoDB error code 40415

Detailed investigation data (common causes, diagnostic steps) is not yet available for this error code. The information above comes from the official MongoDB error code reference.

Related Issues

SERVER-130332Needs Scheduling
Switch participant term transport from $replData.term to dedicated participantTerm field once 9.0 is last-LTS
h3. Context SERVER-128128 carries the participant replication term in {{$replData.term}} rather than a dedicated {{participantTerm}} reply field. This was necessary because adding a new top-level generic reply field and backporting it to older branches causes {{IDLUnknownField}} failures in mixed-version clusters — older mongos binaries use {{strict: true}} IDL reply structs, which reject unknown fields as hard errors. This ticket tracks switching to a dedicated {{participantTerm}} field o
SERVER-130246Closed
Enforce strict: false on IDL reply structs to prevent mixed-version breakage
h3. Background When a new field is added to a command reply via {{generic_argument.idl}} or a dedicated reply IDL struct, an older mongos (or shard acting as sub-router) parses the reply from a newer binary using a strict IDL struct ({{{}strict: true{}}}), and rejects the unknown field with {{{}IDLUnknownField{}}}. This cannot be gated behind FCV because FCV only tracks major.minor, not patch versions. This issue was surfaced in SERVER-128128 and discussed in #server-dev-platform. The cons
SERVER-139159Closed
Remove samplingMethod from analyze calls in analyze_sample_persist_unreplicated.js
SERVER-137870 removed the {{samplingMethod}} and {{numChunks}} fields from the {{analyze}} command and updated the existing tests. {{jstests/noPassthrough/query/query-optimization/analyze_sample_persist_unreplicated.js}} was split out by SERVER-138718 after that PR was branched, and still passes {{{}samplingMethod: "random"{}}}. Both cases now fail with {{IDLUnknownField}} (40415) before reaching the unreplicated-collection check.
SERVER-139102Open
Remove multiversion handling for afterOpTime once 9.0 is not lastlts
Placeholder ticket for making a TODO h3. Background As part of SERVER-29729, the {{afterOpTime}} readConcern field was removed from the IDL and all internal support for it was removed. The {{afterOpTime}} field was the attack surface behind three CVEs. h3. Problem Several JS tests were updated to accept *both* {{ErrorCodes.IDLUnknownField}} (the new behavior, where {{afterOpTime}} is an unknown field) and {{ErrorCodes.FailedToParse}} (the last_lts / v9.0 behavior, where {{afterOpTime