Answer: Check the saved scan's status before starting another scan: in the desktop app open the scan in Scans, or in a Codex conversation ask Codex to check the existing scan. If a wait ends while the scan is still active, return to the same scan or conversation and ask Codex to continue it, and if the scan reports a terminal failure or was canceled, keep the error and saved scan directory. Status: Confirmed Entry: tool/codex/troubleshooting/deep-scan-interruption-failure Revision: 3 Digest: sha256:8f3c846b9eb8a2d2 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:29Z Last changed: 2026-11-19T13:32:19Z (On terminal failure or cancellation: — → keep the error and saved scan directory) Last verified: 2026-11-20T13:42:03Z Next check: 2026-11-21T13:42:03Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of First step | Check the saved scan's status before starting another scan. | [1] | 2026-11-20 Desktop app location | Scans | [1] | 2026-11-20 If wait ends while scan active | return to the same scan or conversation and ask Codex to continue it | [1] | 2026-11-20 On terminal failure or cancellation | keep the error and saved scan directory | [1] | 2026-11-20 Info to include when asking for help | the Codex CLI or desktop app and plugin versions used for the failed run, plus the provider, model, scan status, and exact error | [1] | 2026-11-20 Sources: [1] OpenAI. "Run a deep security scan". https://learn.chatgpt.com/docs/security/plugin/deep-scans.md Role: primary. Accessed: 2026-11-20T13:42:03Z Quote: "Check the saved scan's status before starting another scan." (Supports: First step) Quote: "In the desktop app, open the scan in **Scans**." (Supports: Desktop app location) Quote: "If a wait ends while the scan is still active, return to the same scan or conversation and ask Codex to continue it." (Supports: If wait ends while scan active) Quote: "If the scan reports a terminal failure or was canceled, keep the error and saved scan directory." (Supports: On terminal failure or cancellation) Quote: "include the Codex CLI or desktop app and plugin versions used for the failed run, plus the provider, model, scan status, and exact error." (Supports: Info to include when asking for help) Snapshot SHA-256: 4b0062f844a5f0836d57bd1b8975dfe0e2383c660ad08a78d695b1f65ebc5f77 (captured 2026-11-19T13:32:16Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T13:32:19Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:42:03Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:42:03Z Last attempt: 2026-11-20T13:42:03Z Notes and limitations: Extracted automatically from a single official source (section "Handle an interruption or failure"). Related: https://latestn.com/tool/codex/troubleshooting/desktop-app-config-server-signin What are the limitations of the Codex desktop app when using a configuration server that requires sign-in? https://latestn.com/tool/codex/troubleshooting/exit-codes What exit codes does the Codex Security CLI return? https://latestn.com/tool/codex/troubleshooting/fix-input-monitoring-macos How do I fix Input Monitoring permission issues for Codex Micro on macOS? https://latestn.com/tool/codex/settings/set-reporting-thresholds How do I set reporting thresholds for Codex Security Review? https://latestn.com/tool/codex/settings/set-service-tier-per-turn How do I set the service tier for a single turn in the Codex SDK? https://latestn.com/tool/codex/troubleshooting/codex-diagnostics-env-vars What environment variables can I use to diagnose Codex issues? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:32:19Z | changed | On terminal failure or cancellation: — → keep the error and saved scan directory | [1] 2026-11-19T13:32:19Z | changed | If terminal failure or canceled: keep the error and saved scan directory → — | [1] 2026-11-19T13:32:19Z | changed | First step: Check the saved scan's status before starting another scan → Check the saved scan's status before starting another scan. | [1] 2026-11-17T14:07:17Z | changed | Desktop app location: — → Scans | [1] 2026-11-17T14:07:17Z | changed | If wait ends while scan active: return to the same scan or conversation and ask Codex to continue it → return to the same scan or conversation and ask Codex to continue it | [1] 2026-11-13T03:53:29Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/troubleshooting/deep-scan-interruption-failure/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/troubleshooting/deep-scan-interruption-failure POST: https://latestn.com/dispute/tool/codex/troubleshooting/deep-scan-interruption-failure with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/troubleshooting/deep-scan-interruption-failure?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What should I do if a Codex deep scan is interrupted or fails? Revision 3, last verified 2026-11-20T13:42:03Z. https://latestn.com/tool/codex/troubleshooting/deep-scan-interruption-failure (accessed 2026-11-21T09:59:19Z). @misc{LatestN_tool_codex_troubleshooting_deep_scan_interruption_failure_r3, title = {What should I do if a Codex deep scan is interrupted or fails?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/troubleshooting/deep-scan-interruption-failure}}, note = {Revision 3; digest sha256:8f3c846b9eb8a2d2; last verified 2026-11-20T13:42:03Z; accessed 2026-11-21T09:59:19Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/troubleshooting/deep-scan-interruption-failure