openai / openai/codex

ChatGPT Pro complaint: repeated image-generation blocks, attachment errors, and potential usage-limit deductions

Open
#46,737 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug imagen rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.915.31945

What subscription do you have?

Prto

What platform is your computer?

windows 11

What issue are you seeing?

Hello OpenAI Support,

I am a paying ChatGPT Pro subscriber, and I am reporting repeated failures that have prevented me from completing a straightforward image-generation task.

I requested a photorealistic portrait of a fictional adult woman, approximately 28 years old, based on previously AI-generated reference images. The task was to preserve her facial features, remove any tattoos, and produce a natural-looking portrait. The requested output was a clothed portrait with no nudity or sexual activity.

Three attempts failed with the following error:

HTTP 400
code: moderation_blocked
moderation_stage: output
categories: other

Request IDs:
95311789-4873-4f23-875f-c029049e0c3e
f44e8898-d853-4830-b8e4-102998f657fe
11a0cfe4-ff00-4f33-9cd1-8b2280868875

No image was delivered, and the error messages did not explain the specific reason for the blocks.

Separately, the conversation repeatedly displayed attachment errors:
“Codex could not read the local image (...) No such file or directory (os error 2).”

However, subsequent tool checks located the same files and successfully displayed selected reference images. Please investigate this inconsistent attachment handling as a separate issue.

I am also concerned about usage limits. I cannot verify whether the failed generation attempts or the additional troubleshooting messages reduced my remaining allowance. Please check my account records and confirm this explicitly. If these failures consumed image-generation or other usage allowances, I request that the affected allowance be restored.

I pay for Pro to get useful work done, not to spend repeated interactions troubleshooting failures that produce no result. The lost time, unclear errors, and possible consumption of usage limits are unacceptable for a paid service.

I am not asking for safety safeguards to be bypassed. I am asking for a case-specific review of whether these blocks were justified and for a clear explanation of what went wrong.

Please:

  1. Investigate all three request IDs and explain the specific reason for each block.
  2. Investigate the inconsistent attachment-access errors.
  3. Confirm whether the failed attempts and related troubleshooting consumed my usage allowances, and restore any allowance deducted because of these failures.
  4. Provide a concrete resolution or an estimated timeframe for a fix.
  5. Consider an appropriate service credit or other compensation for the disruption.

Please do not respond solely with a generic suggestion to retry. The task has already been attempted three times with the same outcome. If necessary, escalate this to the relevant technical team.

Kind regards,
Paweł Bis

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a0bc2f-a5ae-7b20-8a38-4d0847768bba

What is the expected behavior?

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with issue #46737, the Codex App version 26.915.31945, and the Windows 11 environment. Review the three request IDs and the reported attachment errors separately, then verify whether failed attempts affected usage limits. Done requires an identified cause or escalation path, clear reproduction details, and confirmation of any allowance impact.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, tooling
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.