missing-key-detonation

The missing key detonation, where the payload is not the model

Code is written against the model in someone's head. The payload is produced by a different system, for a different reason, and for one row, one account, one provider or one mode the field the code treats as always present is simply not there. Direct access explodes.

The same family covers the softer version: the field is present but legitimately null, or an empty array, or a string where a number was expected, and the code that receives it assumed otherwise.

The failed obvious fix for this family is the per symptom guard. Adding an optional access at the crash site stops that crash and leaves every sibling site intact, so the class recurs indefinitely. When you write the diagnosis, name where the contract should be checked, not only where it blew up.

Symptom

A property read on undefined or null, usually as a type error naming the property. The stack points at rendering or mapping code. Most data works; one item, one account or one mode does not. A list renders down to a particular row and stops.

Frequently the reporter describes it as affecting only them, or only one record, which is exactly right and is the most useful thing they said.

What Crumbtrail can see

This archetype is well served, because the payload that caused it crossed a boundary the recorder watches.

• Uncaught errors with the message, the file, the line, the column and the full stack, and unhandled rejections with the message and stack. The property name is normally in the message.
• The response that carried the payload, including its body. Large bodies are summarized and a summary records the original length and why it was reduced. This is the point of the whole sequence: you can read the object the code choked on rather than guess at it.
• Backend response bodies where the backend SDK is installed, so you can see whether the field was already missing when the server produced it.
• Row reads and row changes where the database adapter is installed, which is how you tell a genuinely null column from a field dropped in serialization.