end_user_mismatch
OpenAI input_transformations entry reason: "end_user_mismatch".
What it means
The request that reused this reasoning item had a different safety_identifier from the one that created it (or only one of them had one).
the safety_identifier on the request that created the item differs from the one on the request that reuses it, including supplying an identifier on only one of the two requestsReasoning models (checked 2026-11-19)
Is it yours to fix?
Yes. Your code changed something, so it’s yours to fix.
How to fix it
Send the same safety_identifier on the request that creates a reasoning item and on every request that reuses it, or none on both.
An example that produces it (safety_identifier added on B only):
Earlier request
{
"input": [
{
"content": "Plan the migration.",
"role": "user"
}
],
"model": "gpt-6.2-astra"
}Next request
{
"input": [
{
"content": "Plan the migration.",
"role": "user"
},
{
"encrypted_content": "gAAAABrs_1",
"id": "rs_1",
"summary": [],
"type": "reasoning"
},
{
"content": [
{
"text": "Plan.",
"type": "output_text"
}
],
"role": "assistant",
"type": "message"
},
{
"content": "Go on.",
"role": "user"
}
],
"model": "gpt-6.2-astra",
"safety_identifier": "user_8f3a"
}Related reason codes
prefix_mismatch: prefix_mismatch: GPT-6.2 removed reasoning after a prefix editmodel_mismatch: model_mismatch: reasoning removed after a model switchorganization_mismatch: organization_mismatch: reasoning item from another organizationturn_boundary: turn_boundary: earlier-turn reasoning not used
Last checked 2026-11-19 against the official OpenAI docs.
FAQ
I only added safety_identifier to new requests. Is that enough to trigger it?
Yes. Supplying an identifier on only one of the two requests counts.