[bug] Committing new versions gets stuck every time

[mmabrouk]

@mmabrouk said:

[bug] [Crirical] Commiting new versions don’t work. It get stuck always. cc @arda

CleanShot 2025-12-22 at 17.06.41.mp4

[linear]

AGE-3533

[dosubot]

This issue is most often caused by missing or pending database migrations, which leads to the backend endpoints hanging and the commit process getting stuck in the UI. This has been confirmed in recent reports where errors like relation "organizations" does not exist or column app_variants.hidden does not exist appear in the logs, indicating the database schema is out of sync with the codebase [source].

To resolve this, run the Alembic migrations inside your API container. The recommended command is:

docker exec -e PYTHONPATH=/app -w /app/oss/databases/postgres/migrations <api-container-name> alembic -c alembic.oss.ini upgrade head

You can find more details in the schema migration docs. If migrations fail or the schema is badly out of sync, a workaround is to nuke the Postgres volume, recreate the containers, and apply migrations fresh [source].

This problem is most common in self-hosted/local environments, including Apple Silicon Macs, but is not specific to platform architecture—it's a schema mismatch issue.

If you continue to see the commit process hang after applying migrations, check your backend logs for errors on the /api/variants/{variantId}/parameters endpoint, as the frontend will appear stuck if this call never returns.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}