Hi Vercel team,

I’m seeing what appears to be a stale/orphaned Shareable Link record for a protected deployment.

Project: prj_vsDLlC8wNXxW1XLgPWQxjIQOqVUl Deployment: dpl_8dSDPwAjdii7LCGapBMghrKJtUFo

Exact deployment URL: corvioz-9ukjg199y-jianxu-han-s-projects.vercel.app

Current behavior:

• A Shareable Link was previously created for this exact deployment with a limited TTL.
• The TTL has expired.
• Fresh anonymous access to the deployment is correctly redirected to Vercel Login.
• The exact deployment Share panel currently shows “Only people with access.”
• Team Settings → Deployment Protection → External Access shows “No external access.”
• Copy Link for the exact deployment returns the plain deployment URL with no query parameters.
• Activity history for this deployment shows:
  • alias-protection-bypass-created: 1
  • alias-protection-bypass-regenerated: 0
  • alias-protection-bypass-revoked: 0
• Trying to create another Shareable Link using: PATCH /aliases/{id}/protection-bypass returns HTTP 409, indicating that a Shareable Link already exists.

So the observable state appears inconsistent:

• no active external access in the Dashboard,
• no usable Shareable Link,
• anonymous access is protected,
• but the API still believes a Shareable Link exists and prevents recreation.

I also checked the previously suggested Community workaround using:

DELETE /v1/deployments/{id}/protection-bypass

but that endpoint is not present in the current public REST/OpenAPI reference, and Vercel CLI 58.4.4 rejects it with:

requested API endpoint was not found (404)

I have not disabled Deployment Protection, changed Production aliases, or created another deployment to work around this.

Could someone from Vercel please help confirm:

1. Whether this deployment has a stale/orphaned Shareable Link or protection-bypass record;
2. How that record can be safely removed/revoked;
3. What the currently supported method is to allow a new Shareable Link to be created for this deployment.

Thanks.