Many issues can be diagnosed by reviewing your Runner Agent’s log output. See Troubleshooting Using a Runner Agent’s Logs for instructions on locating and reading logs.
Quick Reference
Failed Inventory Scan
Inventory scans can fail when the credentials in your vault are expired, have insufficient permissions, or when the vault file is outdated. A GitHub outage can also prevent scans from running. For detailed causes and resolution steps, see Failed Inventory Scan.Failed Migration
Migrations can fail for many of the same reasons as inventory scans — expired or under-scoped credentials, outdated vault files, and GitHub outages. Additionally, repository size limitations and invalid destination repository names can cause migration failures. For detailed causes and resolution steps, see Failed Migration.Main Branch Requirement
Warp requires the Migration HQ repository’s default branch to be namedmain. Organizations with a different default branch naming policy will experience runner failures until the branch is renamed.
For the resolution steps, see Main Branch Requirement.
Marketplace Installation Bypass
In rare cases, installing Warp through the GitHub Marketplace may appear to succeed but the app is never installed. A direct installation link is available as a workaround. For the resolution steps, see Marketplace Installation Bypass.Still Need Help?
If these guides don’t resolve your issue, reach out to Product Support via the Support tab in your Project, or contact a Packfiles Partner for expert guidance.