Start with the last successful stage. Repository sync, deployment admission, build, promotion, and runtime health are separate operations; success in one does not prove the next completed.
Setup and connectivity
Deployment problems
Preview problems
A preview requires a same-repository pull request targeting a connected environment’s mapped branch, previews enabled for that environment and the app, and matching input paths when configured. Fork pull requests are not eligible. Sync now can reconcile an existing eligible pull request after a missed webhook.
If an older healthy preview remains online after a failed build, inspect the new deployment’s failure. Towbar preserves the previous healthy preview until a replacement can be promoted. See Preview environments.
Backup and restore problems
Check the relevant cloud provider integration (AWS, Google Cloud, or Azure), bucket/container permissions, object availability, engine version, and available host disk. A stale backup can still be restore-ready; a missing or incompatible object cannot. Read the final restore phase before retrying and confirm whether promotion occurred or rollback completed.
Collect useful diagnostics
Record the Towbar version, Repository and workload IDs, operation ID, timestamps with timezone, and the last failing stage. Include a minimal manifest and redacted logs when opening a GitHub issue.
Do not include secret values, private keys, or database contents. Report suspected vulnerabilities through the private security process. Last modified on September 9, 2026