Failed to generate an LLM response.

[Thomas Hensel]

I am currently testing RovoDev Beta. When I am in a session with "acli rovodev run" I am  getting sometimes the error message "Failed to generate an LLM response." and session stops. Is there a way to get more information about the root cause? How to continue a sesssion after it has been stopped unexpectly?

[Jeremiah Harvey]

Same issue here. The fact that it cannot recover and completely kills the program is upsetting.

[Jovana Dunisijevic]

Hey team

@Thomas Hensel @Jeremiah Harvey 

Our engineering team has run into this error as well and they've been working on the fix! They'll be releasing it very soon, and we'll update you here when that's ready for you to give it another try!

Thank you for coming here to share!

[Riaan Rottier]

I am also getting this error constantly.  I can continue the session via /sessions and then selecting the previous session but it seems to be constantly crashing out at the same point.

[Kun Chen]

Hi everyone! @Jeremiah Harvey @Thomas Hensel @Riaan Rottier 

Thank you for reporting the problem to us - we've been working hard at this. 

We just rolled out a newer version of the CLI that should have made a significant improvement on this! Please download the latest version of acli (instructions available here) and give it a go!

We hope you'll enjoy the smoother experience from here on, but if you ran into any other problems, please don't hesitate to let us know! We really appreciate your feedback. 

[Riaan Rottier]

Just tried with the latest model

- it reports "Network connectivity issue detected, trying fallback model." 

- then tries to repeat the step from a previous session - find it already done

- moves on to the next step - repeats the error "Network connectivity issue detected, trying fallback model."

- and seems to get stuck, missing that the test script is erroring out, not sure if the fallback model is too different from the main model or some data is lost in the transition.

[Kun Chen]

@Riaan Rottier thanks - we'll look into this as well. 

[Shivs]

yep, same here. the previous version got better results. the new one just goes "Network connectivity issue detected, trying fallback model" -> makes the same changes that it reverted earlier and lands at the same error. for me, it's unable to detect npm/ node as well even though its added to the path and runs on powershell/ cmd. makes it difficult to rerun all commands, handover to rovodev and have it fail again.

[Haruna]

I was getting the "Failed to generate an LLM response." and after installing the latest update, I started getting the  "Network connectivity issue detected, trying fallback model." issue. And eventually the "Failed to generate an LLM response." resurfaced again. 

This product is promising but issues like these don't inspire confidence, especially at a time when there are so many realiable tools out there.

Please fix it. 

[Gerrick Bivins]

This was working great until today. The agent was unresponsive and looking for suggestions, I found this thread.

I've updated via homebrew to get to the latest version (1.2.3-stable) but am also seeing the repeated

Network connectivity issue detected, trying fallback model.

My prompt is pretty simple:

Help me implement JIRA {TICKET-#}

[Jeremiah Harvey]

I agree. This worked perfect a couple days ago. Now there are consistent failed response outages. What's going on?

[Peter Wu]

Thank you everyone for reporting this as we look to improve the product and service. This error message is a generic one, and we are implementing better error messaging so it can help us troubleshoot better.

Please try upgrading to the latest version by downloading the latest package. If that does not resolve the issue, please report to us with the following details using this link:

• OS and version

• Shell (i.e. Bash, PowerShell, etc.)

• ACLI version

• acli --version

• Rovo Dev version

• acli rovodev --version

• Rovo Dev log details from

• ~/.rovodev/rovodev.log

• Site url

• Repro steps

• Screenshots (optional)

And we will investigate to resolve the issue.

Thank you for your support and patience.

[Pablo Lebro]

Hi still with the updated version get the error

acli version 1.2.3-stable

OS: Win11 / Powershell

╭─ Network connection issue ───────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Network connectivity issue detected, trying fallback model. │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ An unexpected error occurred, exiting. │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Exception ignored in: <async_generator object HTTP11ConnectionByteStream.__aiter__ at 0x0000023AF430EB40>
Traceback (most recent call last):
File "httpcore\_async\http11.py", line 340, in __aiter__
File "httpcore\_synchronization.py", line 203, in __init__
File "httpcore\_synchronization.py", line 30, in current_async_library
File "sniffio\_impl.py", line 93, in current_async_library
sniffio._impl.AsyncLibraryNotFoundError: unknown async library, or not in async context

[Taner Adak]

Any updates on this?