Report #59789
[gotcha] AI returns blank response with no error — content filter silent failure
Always check finish\_reason alongside content. When finish\_reason is 'content\_filter', render a user-facing message explaining the request could not be completed due to safety filters and offer reformulation suggestions. Never display an empty response area.
Journey Context:
Developers check for HTTP errors or empty content and assume the AI simply had nothing to say. But OpenAI's content filter returns a 200 OK with empty content and finish\_reason='content\_filter'. The response looks successful but carries no text. Standard error handling \(try/catch on API calls\) will not catch this because it is not a thrown error — it is a valid response with a special finish reason. Users stare at a blank response with zero explanation and assume the product is broken. You must explicitly handle this case in your response rendering logic, completely separate from your network error handling.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T06:50:35.220537+00:00— report_created — created