# Codex Security cloud – 409 error after deleting a scan configuration

**URL:** <https://community.openai.com/t/codex-security-cloud-409-error-after-deleting-a-scan-configuration/1391314>\
**Category:** Support\
**Tags:** codex-cloud\
**Created:** [August 19, 2026, 3:32pm UTC](https://community.openai.com/t/codex-security-cloud-409-error-after-deleting-a-scan-configuration/1391314 "2026-08-19T15:32:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alhasan](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@Alhasan](https://community.openai.com/u/Alhasan)\
**Post date:** [August 19, 2026, 3:32pm UTC](https://community.openai.com/t/codex-security-cloud-409-error-after-deleting-a-scan-configuration/1391314/1 "2026-08-19T15:32:13Z")

</div>

Hi,

I’m having an issue with **Codex Security** when trying to create a new security scan for my GitHub repository.

Repository:  
Branch: `main`

When I try to create the scan, I receive the following error:

`Failed to save scan settings: 409: A deleted scan configuration with this ID already exists. Recover it or wait for permanent cleanup before creating a new one.`

The problem is that I cannot find the deleted scan anywhere in **Security → Scans**. The page currently shows **“No scans yet.”**

I have already tried:

- Refreshing the Scans page
- Using a different/new browser session
- Looking for the previously deleted scan
- Looking for a Recover/Restore option

The deleted scan does not appear, so I have no way to recover it, but Codex Security also prevents me from creating a new scan because the deleted configuration apparently still exists in the backend.

Is there a way to:

1. Recover a soft-deleted Codex Security scan configuration that no longer appears in the UI, or
2. Permanently purge the deleted configuration so I can create a new scan for the repository?

I have attached a screenshot showing the exact 409 error.

Thanks.

---

<div class="post-metadata">

**Author:** ![Death.and.Taxes](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/death.and.taxes/32/350971_2.png) [@Death.and.Taxes](https://community.openai.com/u/Death.and.Taxes)\
**Post date:** [August 25, 2026, 3:55pm UTC](https://community.openai.com/t/codex-security-cloud-409-error-after-deleting-a-scan-configuration/1391314/2 "2026-08-25T15:55:07Z")

</div>

Confirming this is still reproducible. I’m seeing the same 409 across three separate repositories in my workspace. I recreated the default Codex environments, refreshed repositories and scans, and verified each repository is on `main`, but every attempt to create a scan still fails with:

`Failed to save scan settings: 409: A deleted scan configuration with this ID already exists. Recover it or wait for permanent cleanup before creating a new one.`

The deleted configurations remain hidden from Security → Scans, and the current UI provides no restore or permanent-delete action. Resetting the local Codex Security workbench did not change the cloud-side state.

Could the Codex Security team confirm whether support can restore or permanently purge these soft-deleted configurations, and whether self-service recovery is planned? I can provide repository IDs and request IDs privately.

---

<div class="post-metadata">

**Author:** ![Death.and.Taxes](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/death.and.taxes/32/350971_2.png) [@Death.and.Taxes](https://community.openai.com/u/Death.and.Taxes)\
**Post date:** [August 25, 2026, 4:26pm UTC](https://community.openai.com/t/codex-security-cloud-409-error-after-deleting-a-scan-configuration/1391314/3 "2026-08-25T16:26:09Z")

</div>

Update: I opened a private OpenAI Support case, and it has been escalated to a support specialist.

I also inspected the low-level network responses. For each affected repository, the repository-specific scan-configuration request returned HTTP 200 with an empty `items` array, while attempting to create the scan still returns the 409 saying that a deleted configuration already exists.

This confirms that the soft-deleted records are filtered at the API layer, not only hidden by the UI. The client receives no configuration ID, route `hid`, or deletion timestamp that would allow self-service recovery.

I supplied the repository IDs, request IDs, and diagnostic evidence privately to Support. I’ll update this thread when the backend records are restored or permanently purged.

---

<div class="post-metadata">

**Author:** ![OpenAI\_Support](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/openai_support/32/561845_2.png) [@OpenAI\_Support](https://community.openai.com/u/OpenAI_Support)\
**Post date:** [October 15, 2026, 8:09pm UTC](https://community.openai.com/t/codex-security-cloud-409-error-after-deleting-a-scan-configuration/1391314/4 "2026-10-15T20:09:17Z")

</div>

Hi @[**Alhasan**](https://community.openai.com/u/alhasan) and @[**Death.and.Taxes**](https://community.openai.com/u/death.and.taxes)! Thanks for sharing all the details and the steps you've already tried.

Just checking in, are you both still running into the HTTP 409 error when trying to create new Codex Security scans?

@[**Death.and.Taxes**](https://community.openai.com/u/death.and.taxes), since you mentioned opening a private Support case and sharing diagnostic information, could you also share the Support Case ID so I can review the existing investigation and avoid duplicating troubleshooting?

-Basil

---

<div class="post-metadata">

**Author:** ![Ba\_sil](https://avatars.discourse-cdn.com/v4/letter/b/c6cbf5/32.png) [@Ba\_sil](https://community.openai.com/u/Ba_sil)\
**Post date:** [October 20, 2026, 11:34am UTC](https://community.openai.com/t/codex-security-cloud-409-error-after-deleting-a-scan-configuration/1391314/5 "2026-10-20T11:34:50Z")

</div>

Closed on October 20, 2026, 11:34am UTC


