Please reconcile the production state of project prj_hAQk2x7AJmahmsIgiAmHlPEDZL2A (ayuchat-superadmin) in team team_PFrjMBSkkORpu8bTYBvC13pr (agnistoka-projects).
Normal promotion of deployment dpl_FE46jTNWpW4rVLZrVRyX96JWjKk8 returns HTTP 409 stating that FE46 is already the current production deployment.
Fresh read-only state on 2026-11-02:
- Custom production domain agnistoka.ayuchat.in serves dpl_H2Sssit5ZiDbNHj8pzhVtLcF9ZJV.
- Project targets.production references dpl_DL4SBWRtMcjLJequC8y76t89rQNB.
- FE46 remains READY/STAGED, target=production, and does not serve the custom production domain.
- The project-slug branch alias points to FE46; canonical ayuchat-superadmin.vercel.app points to DL4.
- Project autoAssignCustomDomains=true; lastRollbackTarget=null; lastAliasRequest=null.
- CLI promote status and rollback status report no active job.
- The promote-aliases read reports the custom hostname pending, despite that null request/status.
- The custom domain is verified, without a branch override, custom environment or redirect.
- FE46 was intentionally staged using --prod --skip-domain; its deployment-level autoAssignCustomDomains=false.
Exact command, Vercel CLI 62.4.0: vercel promote dpl_FE46jTNWpW4rVLZrVRyX96JWjKk8 --yes --scope agnistoka-projects
Documented operation: POST /v10/projects/prj_hAQk2x7AJmahmsIgiAmHlPEDZL2A/promote/dpl_FE46jTNWpW4rVLZrVRyX96JWjKk8
Exact error: The provided deploymentId (dpl_FE46jTNWpW4rVLZrVRyX96JWjKk8) is already the current production deployment. (409)
Please identify why the current-production predicate selects FE46 and either reconcile the project state or provide the supported operation required to make the already-validated FE46 deployment the promoted production target and custom-domain responder. Could the automatic branch alias affect that predicate?
Preserve current H2 traffic until FE46 can safely become production. Do not return traffic to DL4 and do not rebuild FE46. H2 contains required working focus/GSTIN corrections that DL4 lacks. Please do not delete deployments, weaken deployment protection or change unrelated projects.
The candidate already passed authenticated staged acceptance. Source: 9af7b071ca405253ecd0b9dbfd1a1b1f5085bc27. Manifest SHA-256: 931d6004d0e89d6e41517a016cf4cef76c0926d6b0c4df8e28734fc1a6077d2b. All 49 bound artifact files and 48 served static files matched. We are retaining this exact build rather than rebuilding unchanged source to evade the conflict.
We have not repeatedly replayed the failing promotion, changed undocumented metadata, performed an alias-only FE46 cutover or speculatively toggled the already-enabled project auto-assignment setting. Please route this to the deployment/promotion control-plane team if internal reconciliation is required. Additional sanitized evidence can be provided privately. No credentials, tokens, environment values or customer data are included.
A similar state discrepancy was reported at https://community.vercel.com/t/deployment-promotion-409-conflict-candidate-staged-but-cli-reports-already-current/49312 but no supported recovery answer was visible there.
