Pain point · Reliability & bugs · Causes churn
Schema sync can change production product ID and cause outages
1 source thread · first seen 2026-09
Summary
Schema sync between environments using separate license keys can change the production product_id. The author reports that this causes service outages and requires reverting the ID or reimporting the schema to recover.
- Affects
- Teams syncing schemas across production and local or CI/CD environments
- Workaround
- Revert the product_id in the database or reimport the schema; in CI/CD, override the project_id before the server detects the change.
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“this causes the product_id to change live in production, causing massive outages for a ton of our users”