Hello Vercel Community,
How can a client safely reconcile an uncertain deployment-creation result before retrying?
A client attempted one deployment creation, but received no usable creation response and retained no deployment ID or provider request ID. The target was production with autoAssignCustomDomains=false, intended to stage without changing production aliases.
A complete paginated deployment inventory and team activity review found no matching candidate. Existing aliases appear unchanged. We have not retried, promoted, deleted, or cleared the pending-intent record. We do not treat an empty list as proof of non-creation.
Questions:
- Is there an authoritative API/dashboard method to find the result, including failed, deleted, or still-pending records, when the deployment ID is unknown?
- Can client-supplied metadata reliably reconcile this? What visibility or retention limitations apply?
- Is there a documented idempotency mechanism for deployment creation? Otherwise, what evidence makes a retry safe without duplicate deployments?
- For a Hobby account without technical support ticket access, is there an official private channel for diagnostic identifiers if provider-side lookup is required?
Project/account names, IDs, transaction values, source contents, and credentials are intentionally omitted. This is a request for guidance and read-only verification, not permission to create, promote, delete, or modify deployments.
Thank you.