Affected feature and model, if relevant: GPT 6 Pro
Bug
Repeatedly, a request for GPT 6 Pro leads to ‘Thinking failed’ errors. In fact, this happens on more than 50% of my queries, and leads to hours of wasted effort.
There is now an official status incident that overlaps part of this thread, which gives us a useful timing boundary.
OpenAI Status recorded “Elevated Error Rates on GPT-6 Astra Pro” on September 24:
identified: about 18:59
monitoring after mitigation: about 19:32
resolved: about 19:46
That overlaps the evening reports here around 19:12 and 19:18, so those failures should be treated as incident-confounded rather than clean evidence of some separate account-specific cause.
But it does not explain the whole report, because the original post says the “Thinking failed” problem has been happening for months and on more than half of queries.
So I would split the evidence into three windows:
before the official Sep-24 incident;
during 18:59–19:46;
after the status page says the incident was resolved.
The most useful next evidence is not another large batch of attempts. It is one naturally occurring post-resolution failure with:
exact local timestamp/timezone;
selected model/mode;
surface (Web/iOS/macOS);
exact “Thinking failed” text or screenshot;
whether the failed request still consumed one of the Pro-message allowances.
If failures continue after the official recovery window, that separates the chronic issue from the known Sep-24 outage.
And I would keep “Thinking failed”, rate-limit accounting, and model-routing/substitution as separate questions unless native evidence actually ties them together.