Symptom: the recorded version of a resource and the version actually in use disagree.
This is a records problem before it is a technical one. If the version you are working from is not the version you think it is, every other statement attached to that record — compatibility, revision, firmware relationship — describes something else.
Likely causes
- A resource that has changed since it was recorded. The record is accurate for its review date, not for now.
- A stale record. The review date on the record is old, so its version statement is historical.
- Two similar resources confused. Categories of keyset and tool look alike; the label on the record may not match the artefact in hand.
How to confirm
Check the review date attached to the record. Where a version has not been confirmed, the version field reads “not published” — that is a statement about the record, not a defect. Compare against the versions hub and the update policy, which describes how records are re-checked.
Where this connects
Version records feed directly into compatibility, so read the compatibility hub next. If the mismatch produces a failure at the decryption stage, see decryption errors.