{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihc626cmifop2qpq2c22le2jqcpkaakt5bife4vvnghkwbucenv2m",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mju2rdu5zdi2"
  },
  "path": "/t/upgraded-to-pro-and-get-hit-with-usage-limit-error/1379259#post_3",
  "publishedAt": "2026-04-19T12:49:05.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "OpenAI Codex GitHub Issues tab",
    "Entire 5-Hour + 22% Weekly Limits + All Credits Burned Without Running · Issue #11508 · openai/codex · GitHub",
    "Codex features are prioritized by votes in GitHub issues tab",
    "Codex",
    "Source"
  ],
  "textContent": "Welcome to the forum!\n\nYou can discuss Codex-related issues here, but the official place to report them is the OpenAI Codex GitHub Issues tab.\n\nI checked for a closely related report and found:\n\n  * Entire 5-Hour + 22% Weekly Limits + All Credits Burned Without Running · Issue #11508 · openai/codex · GitHub\n\n\n\nThat issue includes comments from etraut-openai with some useful context and guidance.\n\nIf it matches your situation, consider adding a  reaction to increase visibility.\nIf not, it’s worth searching existing issues; if nothing aligns, open a new report with clear reproduction details.\n\n* * *\n\nAlso take a look at\n\nCodex features are prioritized by votes in GitHub issues tab Codex\n\n> FYI We prioritize feature requests based on upvotes from the community. If a feature request doesn’t get enough upvotes, we’ll close it. It’s therefore important for a feature request to have a clear and compelling title and description. We also recommend that feature requests focus on the problem statement rather than a solution. Describe the use case and what problem you’d like to see solved. There are often multiple ways to address a given problem. Source Note: In GitHub feature request…",
  "title": "Upgraded To Pro And Get Hit With \"Usage Limit\" Error"
}