Help
Troubleshoot the release gate without leaking evidence.
Public help content explains what to do next while keeping release records, operator names, and protected control-plane details inside authenticated workflows.
A release is on HOLD
Check the missing evidence list first. Most HOLD decisions need a verified image digest, rollback path, or healthy runtime target.
Add evidence, rerun the gate, then publish an updated release note.
A release is BLOCKED
Treat BLOCK as a production-safety stop. Name the owner, capture the reason, and avoid bypass unless this is an approved emergency.
Escalate to the release approver and record the final decision.
Stakeholders need an update
Use the short status format: current verdict, affected service, owner, next action, next update time, and rollback readiness.
Send a concise note and link to the protected passport when the recipient has access.
Support handoff template
Use this when a customer cannot complete onboarding, publish a release note, or understand a gate result.
Public-safe error copy
Missing rollback evidence
Add a rollback reference before requesting approval.
Runtime target unavailable
Wait for the target to report ready, then rerun the gate.
Permission required
Sign in with an approved Release Passport account to view protected evidence.
Empty and permission states
No passports yet
Create the first passport from a published template, or ask a workspace owner to publish one first.
No templates published
Use the protected console template flow to save a draft, compare versions, simulate policy impact, then publish.
No assigned actions
There are no approvals, reminders, or validation tasks assigned to your account. Check the command center.
Permission required
Sign in with an approved workspace role. Public pages cannot show release evidence or owner-only controls.
Release note
Use the changelog template for stakeholder-ready status.
Rollback path
Keep the rollback reference in the protected passport and summarize it safely.
Known risk
Name blockers and next action without exposing private evidence.
Still blocked?
Send a public-safe request. Keep tokens, private evidence, and operator credentials out of email.