Hey @Sivaram Gollapudi
Thanks for reaching out and for trying out Rovo Dev Code Review.
Since it was posting suggestions at first and then stopped about 10 days later, it’s usually one of these issues:
Code review isn’t being triggered anymore
- In your repository settings, please confirm that Rovo Dev Code Review is still enabled and that the trigger is what you expect (for example: “Only when pull request is created”, or “When pull request is created and on each commit”).
- If your repo is set to “Don’t review automatically”, you’ll only get reviews when the PR author manually triggers them.
-
No comments doesn’t always mean it didn’t run
- Rovo Dev will only comment when it finds potential issues or improvements. If the code looks good and it doesn’t have actionable feedback, it won’t leave any comments on the pull request.
- To verify if it’s running, in Bitbucket you can:
- Open the pull request
- Look for the Rovo Dev section on the Overview tab and click Review code (if available)
- Wait a few minutes and refresh to see if comments appear.
The pull requests might be too large
- If a pull request has more than 10,000 lines of changes or the repository is larger than 20 GB, Rovo Dev may skip leaving comments (or just comment that the PR is too large).
- If that might be the case, try splitting the PR into smaller parts and see if comments resume.
Rate limit or credit limit reached
- Rovo Dev can review about 10 pull requests per minute per workspace. If a lot of PRs were created/updated in a short window, some might not be reviewed.
- If you’ve reached your Rovo Dev credit limit, Rovo Dev will stop reviewing until usage resets or your admin increases the credit allocation.
- Your admin can check Rovo Dev credit usage and subscription status from the Atlassian admin screens (Rovo Dev section).
-
Temporary system or configuration issues
- There can be a temporary system error, or the feature may have been toggled off/on in the workspace or repo.
- A practical step is to:
- Turn Code Review off and back on again for the affected repository
- Create a small test pull request with an obvious issue (for example, a typo or bad variable name) and see if Rovo Dev comments on that.
I hope this is helpful, let me know how you go!
Jov
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.