Answer: To resume a campaign, run the original command with the same CSV and output directory; the CLI resumes the campaign, starting new attempts for eligible unfinished repositories and skipping completed scans. Don't change the repository inventory or scan and follow-up instructions for an existing output directory, since the CLI checks the pinned manifest and rejects a different campaign. Status: Confirmed Entry: tool/codex/troubleshooting/resume-bulk-scan-campaign Revision: 2 Digest: sha256:f07d17fb87a0687e (changes whenever the content changes) Timeline: Created: 2026-11-13T03:52:58Z Last changed: 2026-11-20T13:41:30Z (When to use new output directory: — → Use a new output directory when you change repositories,) Last verified: 2026-11-20T13:41:30Z Next check: 2026-11-21T13:41:30Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Resume method | Run the original command with the same CSV and output directory | [1] | 2026-11-20 Resume behavior | The CLI resumes the campaign, starting new attempts for eligible unfinished | [1] | 2026-11-20 Completed scans | skipping completed scans, including scans with coverage gaps | [1] | 2026-11-20 Manifest check | The CLI checks the pinned manifest and rejects a | [1] | 2026-11-20 When to use new output directory | Use a new output directory when you change repositories, | [1] | 2026-11-20 Sources: [1] OpenAI. "Run bulk security scans". https://learn.chatgpt.com/docs/security/cli/bulk-scans.md Role: primary. Accessed: 2026-11-20T13:41:30Z Quote: "Run the original command with the same CSV and output directory:" (Supports: Resume method) Quote: "The CLI resumes the campaign, starting new attempts for eligible unfinished" (Supports: Resume behavior) Quote: "repositories and skipping completed scans, including scans with coverage gaps." (Supports: Completed scans) Quote: "The CLI checks the pinned manifest and rejects a" (Supports: Manifest check) Quote: "Use a new output directory when you change repositories," (Supports: When to use new output directory) Snapshot SHA-256: 70a62735c3bba216c96f7e1dc571de575dc489904d55f86100f004f5227f0dc9 (captured 2026-11-19T13:31:45Z) 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:31:46Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:41:30Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:41:30Z Last attempt: 2026-11-20T13:41:30Z Notes and limitations: Extracted automatically from a single official source (section "Resume a campaign"). Related: https://latestn.com/tool/codex/troubleshooting/security-plugin-disabled-by-admin How do I fix a Codex Security plugin that shows 'Disabled by admin' in a managed workspace? https://latestn.com/tool/codex/troubleshooting/troubleshoot-agents-md-discovery How do I troubleshoot Codex not picking up my AGENTS.md instructions? https://latestn.com/tool/codex/troubleshooting/troubleshoot-gateway-connection How do I troubleshoot a Codex gateway connection that isn't working? https://latestn.com/tool/codex/troubleshooting/large-repos-slow-in-wsl Why do large repositories feel slow in WSL when using Codex? https://latestn.com/tool/codex/troubleshooting/migrate-nfs-home How do I migrate an existing Codex home directory on NFS to avoid SQLite corruption? https://latestn.com/tool/codex/troubleshooting/report-issues-request-features Where do I report issues or request features for Codex? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:41:30Z | changed | When to use new output directory: — → Use a new output directory when you change repositories, | [1] 2026-11-20T13:41:30Z | changed | Manifest check: — → The CLI checks the pinned manifest and rejects a | [1] 2026-11-20T13:41:30Z | changed | Completed scans: — → skipping completed scans, including scans with coverage gaps | [1] 2026-11-20T13:41:30Z | changed | Resume behavior: — → The CLI resumes the campaign, starting new attempts for eligible unfinished | [1] 2026-11-20T13:41:30Z | changed | Resume method: — → Run the original command with the same CSV and output directory | [1] 2026-11-20T13:41:30Z | changed | new output directory: Use a new output directory when you change repositories, → — | [1] 2026-11-20T13:41:30Z | changed | manifest check: The CLI checks the pinned manifest and rejects a → — | [1] 2026-11-20T13:41:30Z | changed | warning: Don't change the repository inventory or scan and follow-up instructions for → — | [1] 2026-11-20T13:41:30Z | changed | skipped scans: skipping completed scans, including scans with coverage gaps → — | [1] 2026-11-20T13:41:30Z | changed | resume behavior: The CLI resumes the campaign, starting new attempts for eligible unfinished → — | [1] 2026-11-20T13:41:30Z | changed | resume method: Run the original command with the same CSV and output directory → — | [1] 2026-11-13T03:52:58Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/troubleshooting/resume-bulk-scan-campaign/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/resume-bulk-scan-campaign POST: https://latestn.com/dispute/tool/codex/troubleshooting/resume-bulk-scan-campaign with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/troubleshooting/resume-bulk-scan-campaign?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I resume or retry a Codex Security bulk scan campaign after it is interrupted? Revision 2, last verified 2026-11-20T13:41:30Z. https://latestn.com/tool/codex/troubleshooting/resume-bulk-scan-campaign (accessed 2026-11-21T10:03:27Z). @misc{LatestN_tool_codex_troubleshooting_resume_bulk_scan_campaign_r2, title = {How do I resume or retry a Codex Security bulk scan campaign after it is interrupted?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/troubleshooting/resume-bulk-scan-campaign}}, note = {Revision 2; digest sha256:f07d17fb87a0687e; last verified 2026-11-20T13:41:30Z; accessed 2026-11-21T10:03:27Z} } 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/resume-bulk-scan-campaign