Rovo Dev Down?

[Ash McConnell]

Hi Folks,

Is Rovo Dev down at the moment?  I tried upgrading to the latest version and logging out and in again, but every question I ask results in a blank answer and the number of tokens left being shown.

Is it just me?  Any suggestions on getting going again?

Thanks!
Ash

[Jovana Dunisijevic]

Hey @Ash McConnell 

Thanks for reaching out and sorry to hear you’re having trouble with Rovo Dev CLI!

Current Status:
There is no known outage affecting Rovo Dev CLI at the moment. However, the CLI is currently in beta, and there are some known issues that can cause blank answers or only show the number of tokens left.

What might be happening:

• Token Limits: If you’ve hit your daily token limit, the CLI may stop responding to prompts and only display your remaining tokens. You can check your usage by running the /usage command in interactive mode.

• Beta Improvements: There are some bugs and edge cases being tracked, especially around setup, authentication, and large codebases. These can sometimes cause the CLI to become unresponsive or return blank answers.

What you can try:

1. Check your token usage: Run /usage in the CLI to see if you’ve hit your daily limit. More info: https://support.atlassian.com/rovo/docs/token-limits-and-usage-in-rovo-dev-cli/

2. Check your logs: Look for errors in <your home directory>/.rovodev/rovodev.log.

3. Windows-specific: If you’re on Windows, try authenticating via Command Line instead of PowerShell, as there are known issues with token pasting and authentication in PowerShell.

4. Restart the CLI: Sometimes a fresh session helps.

5. Report a bug: If the issue persists, please report it (including your log file) here: Bug report - Rovo Dev in CLI

I hope this helps fix things for you!

Kindest regards,

Jov

[Ash McConnell]

Hi @Jovana Dunisijevic 

Thanks for the help!

I've used 0 tokens for today, so that's not it.  I looked at the logs and there doesn't seem to be anything overly suspicious that I can see.

I've restarted the CLI a few times.  I'll raise a bug when I'm on that machine later on

Thanks!

Ash

[Ash McConnell]

Hi Folks, 

I managed to make this work again by removing the ~/.config/acli folder and logging in again.

Hope this helps some googlers :)

All the best,
Ash