access to gpt-5.3-codex-premium-1p-codexswic-ev3 blocked?
Resolved 💬 2 comments Opened Mar 3, 2026 by taf2 Closed Mar 3, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
was just reviewing code - auth code yes... but still:
• Confirming token refresh logic and potential SOQL injection concern
• Explored
└ Search determine_owner_id_for_call\( in app
Search determine_owner_id_for_call in app
Search \.hideFooter() in javascripts
Search class=\"filter-body\"\|workflow_filter in internal
Read filter.mustache
Search route_type.*SmsBot\|SmsBot in models
Read message.rb
• Ran ruby -c app/models/sms_bot.rb && ruby -c app/models/sms_bot_session.rb && ruby -c app/models/trigger_salesforce_link.rb && ruby -c app/models/trigger_salesforce_mcp.rb && ruby -c app/models/trigger_scheduled_action.rb && ruby -c
│ app/models/trigger_voice_ai_call_action.rb && ruby -c app/controllers/api/v1/salesforce_controller.rb && ruby -c app/controllers/oauth2_controller.rb
└ Syntax OK
Syntax OK
… +4 lines
Syntax OK
Syntax OK
• Explored
└ Search def process!\|def process_upsert\|return ret\|@record_id in trigger_salesforce_link.rb
Read trigger_salesforce_link.rb
List mcp
Search ctm-salesforce-reads-v1.2026.json in .
Search mcp/ in .
■ stream disconnected before completion: This user's access to gpt-5.3-codex-premium-1p-codexswic-ev3 has been temporarily limited for potentially suspicious activity related to cybersecurity. Learn more about our safety mitigations:
https://platform.openai.com/docs/guides/safety-checks/cybersecurity
<< Code review finished >>
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
• Review was interrupted. Please re-run /review and wait for it to complete.
• Feedback uploaded. Please open an issue using the following URL:
https://github.com/openai/codex/issues/new?template=2-bug-report.yml&steps=Uploaded%20thread:%20019cb143-d52f-7893-9db9-dc767c5eab8b
Or mention your thread ID 019cb143-d52f-7893-9db9-dc767c5eab8b in an existing issue.
2 Comments
Thanks, we're looking into the cause and will report back when it's mitigated. Apologies for the disruption.
The problem has been mitigated. We're resetting rate limits to compensate everyone for the inconvenience.