Sites deployment fails with SQLITE_ERROR without identifying the failed migration

What version of the Codex App are you using (From “About Codex” dialog)?

26.905.11957

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Windows, OS version 10.0.26200.0, x64

What issue are you seeing?

My first owner-only private deployment of a ChatGPT Site failed with:

incomplete input: SQLITE_ERROR

The local build and version saving succeeded, but deployment failed and no live URL was returned.

The error does not identify the failed migration file or SQL statement. I cannot determine which migrations, if any, were applied before the failure.

Read-only diagnostics:

• Database overview returned bindings=[], tables=[], and selected_binding_name=null, with no omitted results.
• Worker logs returned 409 worker_logs_unavailable.
• A database overview recheck on September 10, 2026 returned the same empty result.

I have not reset the database, rewritten the migrations, or retried the failed deployment because the applied migration state is unknown.

The root cause is not established. Please help identify the failed statement and the database's migration state.

What steps can reproduce the bug?

Steps taken in the affected project:

1. Prepare a D1-backed Site using the bundled Sites workflow in the Windows desktop app.
2. Configure the logical D1 binding as "DB".
3. Include these generated migrations:
   • drizzle/0000_free_luminals.sql
   • drizzle/0001_thin_risque.sql
4. Build and package the project successfully.
5. Save the version successfully.
6. Deploy the saved version with owner-only private access.
7. Observe deployment failure: incomplete input: SQLITE_ERROR.
8. Request the database overview and Worker logs; neither reveals the applied migration state or the failed SQL statement.

One migration includes CREATE TRIGGER statements, but I have not established whether that is related to the failure.

This describes the affected project, not an independently verified minimal reproduction.

What is the expected behavior?

If a migration fails, the deployment error should identify:

• The migration file and failed SQL statement.
• Which migrations were successfully applied.
• Whether any statements in the failed migration remain applied.
• The supported recovery procedure.

This information is needed to correct the failure without overwriting migration history or resetting the database.

Additional information

The deployment failure was recorded on September 9, 2026 at approximately 06:10 UTC.

I submitted in-app feedback but did not retain the feedback ID.

No real student or research data has been collected. The Site remains private and research collection is disabled.

Deployment identifiers are retained and can be supplied through a private support channel if needed. No credentials or personal data are included in this report.

Start with the bundled Sites workflow and reproduce the failure using drizzle/0000_free_luminals.sql and drizzle/0001_thin_risque.sql with the logical DB binding. Compare the deployment result with the migration state and the migration containing CREATE TRIGGER statements. Done means the failure identifies the migration and SQL, reports applied statements or migrations, and documents recovery guidance.