Failed to generate an LLM response

[Kōtarō Bokuto]

While using rovodev on version 1.3.0, when given a prompt rovodev fails to generate a response.

[Paweł Ruta]

Same for me. Error appears frequently, every few seconds. Sometime even rovodev can't start and gives:

Rovo Dev Agents is not installed on your site

To use Rovo Dev CLI, your organization administrator needs to install Rovo Dev Agents

Just starting again and it works. But again after a few seconds crash with error

Failed to generate an LLM response

Previous version what very stable.

[ratihabition3006]

I have been hitting this error almost every few minutes after upgrading to acli 1.3.0

Intermittently the following error is observed:

Rovo Dev Agents is not installed on your site

To use Rovo Dev CLI, your organization administrator needs to install Rovo Dev Agents.
Visit https://www.atlassian.com/try/cloud/signup?bundle=devai to request access.

[ghost_index_21]

Same issue on both previous and latest acli versions.

I can login fine and some requests do go through but eventually run into this error:

Failed to generate an LLM response

[Luca]

Same as above. Sometimes it does't even run it. It all started when Daily Token Limits change was first displayed. It worked extremely well for almost a month and now in the last couple od day it crashes every 3 to 5 minutes at the most.

[Paweł Ruta]

Yesterday, with the same version there was no errors. Maybe it was something on the backend side on Friday? It would be great if, when such an error occurs, the application doesn't crash - instead, try three retries, and if those fail, simply wait for user input instead of exiting.

[Jovana Dunisijevic]

Hi everyone!

Thank you for reporting this issue while using Rovo Dev. This is a known error message that can occur for a few different reasons, especially while the CLI is in beta.

1. Common causes:

   • Sometimes this error is triggered by a temporary backend or service-side issue.

   • It can also happen if the codebase is very large. Try running Rovo Dev in a smaller subdirectory with fewer files to see if that helps.

   • If you’re hitting rate limits or see errors about “Too Many Requests,” waiting a few minutes and trying again can help.

2. Known issues and fixes:

   • If you’re on Windows and using PowerShell, try running the CLI in the standard Command Prompt instead.

   • Make sure you’re using the latest version of the CLI.

   • If you recently updated your API token or configuration, try logging out and back in.

3. Check the log file:
   Rovo Dev CLI writes detailed logs to ~/.rovodev/rovodev.log. Reviewing this file can help pinpoint what’s going wrong. If you’re comfortable, please share any relevant error details from the log here (removing any sensitive info).

4. If the problem persists:

   • Please attach the relevant section of your rovodev.log file so the team can help investigate further.

   • You can also report a bug directly via the https://support.atlassian.com/rovo/docs/troubleshoot-problems-with-rovo-dev-cli/

We also have release the latest version recently of the CLI (which is now 0.10 https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/Rovo-Dev-CLI-v0-10-Release-Notes/ba-p/3086569) that includes various bug fixes and stability improvements.

Give that a go and let me know if it works better for you all now!

Kindest regards,

Jovana