Missing PR comment
Diagnose failed GitHub App webhook deliveries without exposing credentials.
When the Mission Control comment is missing, start with the matching GitHub
pull_request delivery for that repository and time. An installation
delivery can succeed while the affected pull-request event continues to fail.
Examine the affected delivery
- Open the Lifecycle GitHub App’s Advanced settings.
- In Recent deliveries, select the
pull_requestevent for the affected repository and action. - Record the non-secret delivery ID, event, action, timestamp, response status, and response message.
- Make sure that the target is the configured Lifecycle webhook URL.
- Make sure that its TLS certificate is valid.
If no matching delivery exists, make sure that:
- an App installation includes that repository
- the App subscribes to pull-request events
- the App has the documented repository permissions
- the repository is onboarded in Lifecycle
Do not create a different pull request at this time. Keep the first failed delivery so the request and response stay correlated.
Match the Lifecycle request
Set the Helm release and namespace used by the installation, then search recent web logs for the GitHub delivery ID:
Use the response and matching log message to select the next check:
| Evidence | Next check |
|---|---|
| DNS, connection, or TLS failure | Correct the public webhook hostname, DNS, certificate, or ingress path |
| Signature or credential error | Bootstrap Secret key presence and the approved credential-rotation workflow |
| Repository ignored or not found | Make sure of App access and Lifecycle onboarding |
| Accepted delivery but no comment | Examine the worker queue and the affected Environment using stuck Environment |
When you share evidence, include the delivery ID and status. Do not include payload secrets, signatures, authorization headers, or private repository content.
GitHub App key check
When the response or Lifecycle log points to GitHub App configuration, run this procedure.
Lifecycle computes the bootstrap Secret name from the Helm release. You can override this name. Use chart labels to find it:
Make sure that the expected keys exist. Do not decode or print their values:
The key list must include the necessary GITHUB_* entries. If a value can be
incorrect, use the secure installation procedure to rotate it. Do not paste
decoded secrets into terminals, tickets, or chat.
Correction check
After you correct the identified cause, redeliver the same failed GitHub delivery. Make sure that it receives a success response. Make sure that Lifecycle creates or updates the Mission Control comment.
Only if the approved procedure specifies a restart, restart the component. Key presence alone is not a reason to restart the web and worker deployments.
A second delivery can queue duplicate work after a response timeout. Before you redeliver, examine the Environment and queue state.