Troubleshoot Rose
Start with the section that matches what you see. If you contact support, include the repository, the step you attempted, and the approximate time.
Owner approval is pending
If you requested the GitHub App installation, a GitHub organization owner must approve it before setup can continue. After approval, return to OllyGarden and continue the Connect GitHub flow.
OAuth or setup needs another try
Return to OllyGarden and start Connect GitHub again. Make sure you’re signed in to the intended OllyGarden and GitHub organizations and complete every GitHub confirmation screen. If another attempt fails, note the approximate time and contact support.
A repository is missing
First check the Rose GitHub App installation in GitHub. If the app can’t see the repository, grant access there. Then return to OllyGarden and activate the repository. Remember that GitHub App access and Activate are separate steps.
A Review does not start
Confirm that the repository is active in Rose, not only available to the GitHub App. Scheduled reviews may skip a repository that has not changed. If Run review is shown but unavailable, use the availability time displayed by Rose.
A Review failed
Retry when Run review becomes available. If it fails again, record the repository and approximate time, then contact support. Your earlier findings remain available while you wait.
The GitHub dashboard issue is missing
Check whether GitHub Issues are enabled for the repository. You can still open findings and use Fix in OllyGarden without a dashboard issue.
A finding does not apply
Read the explanation and surrounding code first. If the finding still does not fit, dismiss it. You can restore it later. For a repeated project-specific convention, consider a custom rule.
A fix failed
The selected findings remain active when Rose cannot prepare a change. Try a smaller set or use Copy prompt. If repeated attempts fail for the same finding, contact support rather than starting several overlapping fixes.
A pull request follow-up does not start
Check that the pull request is open and was created by Rose. Add a new general pull request comment that starts a line with the Rose App mention shown for your installation. Inline review comments provide context but do not start a follow-up. The commenter must have write access to the repository.
A custom rule is rejected
Keep the rule under 4,000 characters. Remove links, network destinations, and language that tries to override Rose’s instructions. Rewrite it as one clear, testable check, then save it again.
Contact support
Still stuck? Email support@ollygarden.com with your OllyGarden organization, repository, the step you attempted, and the approximate time. Don’t send credentials, access tokens, API keys, or secrets.
Return to the Rose overview for the complete workflow.