tasks vanished (from log aswell)

[andott28]

App Version

3.16.3

API Provider

Not Applicable / Other

Model Used

gemini pro 2.5 exp 03 25 // gemini 2.5 pro prev 05 06

Actual vs. Expected Behavior

after completeing a task within roo code it just vanished. I have tried finding it but it is gone. After doing this I tried making a project completely from scratch but it soon vanished aswell.

It might have to do with adding a paid configuration profile. since it hadn't happened before.
Might also be something with the new version since i updated. (note: it happened even after downgrading to the second newest version, so take it as you may).

Detailed Steps to Reproduce

Relevant API Request Output or Error Logs

Additional Context

No response

[dosubot]

Hello @andott28! I'm Dosu, your friendly bot here to help you solve bugs, answer questions, and assist you on your journey as a contributor while you wait for a human maintainer. Let's tackle this together! 🤖

There are known issues related to task disappearance in the Roo Code repository. One issue occurs when using Roo Code v3.3.26 with Claude 3.5 Sonnet, where clicking on any task in the recent tasks list causes the task to be deleted without confirmation, instead of showing the task details. This issue was reported but resolved itself after rebooting the system, indicating it was caused by a temporary system state. Additionally, there is a known bug in VS Code v3.9.2 that causes Roo task history to be cleared when connecting to WSL (Ubuntu 22.04.5 LTS), with the message 'Cleaned up 1 task(s) with missing files from history.' This issue has been fixed in VS Code v3.10.0, so upgrading to this version or later can prevent the problem ^[1][2].

Regarding version 3.16.3, I couldn't find specific changes related to task persistence in the repository. However, if the issue persists even after downgrading, it might be related to the configuration profile or other system-specific factors. It could be helpful to check if there are any open issues or discussions related to version 3.16.3 in the repository.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[andott28]

As a follow-up:
I have found a related issue (#3348 (comment)), which also uses Gemini.

I tried the troubleshooting steps but the problem still persists.

[halhenke]

I was the one who reported #3348 and I just "lost" another task which no longer shows up in the UI History.

Have tried to locate the Task on disk (~/Library/Application Support/Code/User/globalStorage/etc) but its not there with the other tasks.

Its hard to compare the way i use Roo to others but it may be related to Tasks that grow particularly large. As mentioned am using Gemini 2.5 and sometimes i like to let the context get quite large.

[andott28]

I was the one who reported #3348 and I just "lost" another task which no longer shows up in the UI History.

Have tried to locate the Task on disk (~/Library/Application Support/Code/User/globalStorage/etc) but its not there with the other tasks.

Its hard to compare the way i use Roo to others but it may be related to Tasks that grow particularly large. As mentioned am using Gemini 2.5 and sometimes i like to let the context get quite large.

I have found somewhat of a workaround. It does not work to get back a removed task, but if the task shows up in the "recent tasks" (shows up but not clickable), it might be retrievable.

I have found that if you change the extension version before doing anything else, it will write itself back somehow. I don't know when this works, but it has worked some of the times I have tried.

Further, I think the reason is with the paid Google Gemini. Since I have two versions, one paid and one not. The error has only occurred with the paid profile and not in the free profile.

[hannesrudolph]

Can either of you please provide detailed steps to reproduce so we can look into it? This sounds frustrating and I am sorry it's not working as intended.

[halhenke]

@hannesrudolph Will try to be more observant but its difficult as this is a sporadic thing that hasnt happened with the vast majority of tasks

I do suspect it may be related to #3508 as the way i am using gemini at least i run into a lot of RESOURCE_EXHAUSTED errors and am fairly frequently hitting Cancel Task to get out of a retry loop and switch Providers - maybe this also rings true for @andott28?

[andott28]

@hannesrudolph Will try to be more observant but its difficult as this is a sporadic thing that hasnt happened with the vast majority of tasks

I do suspect it may be related to #3508 as the way i am using gemini at least i run into a lot of RESOURCE_EXHAUSTED errors and am fairly frequently hitting Cancel Task to get out of a retry loop and switch Providers - maybe this also rings true for @andott28?

Yes this is completely true. I am switching between the free google gemini 2.5 pro and the paid version.

Both are 2.5 pro but paid is the "2025.05.06" and the free one is "2025.03.05" i believe.

I am using them through Vertex AI on both aswell. Maybe some of this has a coorelation?

[James-Cherished]

Hi, same here.
I have also encountered similar issues since around version 3.16

A new issue happened with version 3.16.6, where not the whole task but considerable chunks are disappearing : #3508 (comment)

I am using a lot of Gemini, both through OpenRouter and Google, with different keys. Boomerang Mode switching to different modes causes different models and keys to be used throughout the task, because of sticky models (an option it might be beneficial to be able to opt-out from). The specifics of Gemini's unreliability causes a lot of failed requests.
To switch, we currently have to cancel the task. Those repeated cancellations might be the cause of the data losses.
I also think it might be beneficial to be able to change model while waiting for an API reply, just like we have the ability to change Mode.

Thanks!

Edit: one last beneficial tweak: not resuming a Boomerang task after a subtask was manually canceled without letting the user state the reason. The automatic API call after having to close a subtask can be frustrating, I've created a new issue for more details here: #3617