Skip to main content

Bridge Won't Deploy

Updated this week

Common Causes

Pending Secrets

Error: "Cannot deploy: pending secrets require customer input"

Fix: One or more linked secrets haven't been provided by the customer yet. Check the Secrets tab to see which secrets are pending. Either wait for the customer to provide values via the portal, or switch the secret to SE-managed and provide the value yourself.

Expired Secrets

Error: "Cannot deploy: some linked secrets have expired"

Fix: One or more linked secrets have passed their expiration date. The customer needs to provide new values, or you need to update the expiration date.

Deploy Limit Reached

Error: "Deploy limit reached: X/Y active bridges"

Fix: Your organization has hit its active bridge limit. Either upgrade your plan to add more bridge slots, or pause/archive an existing active bridge to free up a slot.

Critical Security Issues

Error: "Deployment blocked: X critical security issue(s) must be fixed"

Fix: The security review found critical vulnerabilities in your code. Check the Security tab for details. Common issues include hardcoded API keys or tokens β€” move these to proper secrets.

Pending Approval

Status shows "Pending Approval"

Not an error. Your organization requires admin approval for deployments. An admin needs to approve the deploy from the bridge detail page. If rejected, you'll see the rejection reason on the bridge page.

Did this answer your question?