Part way through working on a project and it fails with error message and now cannot continue
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
### Short summary
Part way through working on a project and it fails with error message and now cannot continue
### Affected version or release
v0.2.23
### Installation context
Installed on Windows 11
### What happened?
Error: Execution failed: CAPIError: 400 {"error":{"code":"bad_request","type":"websocket_error","message":"[ApiIdParam] [input[1].id] [string_above_max_length] Invalid 'input[1].id': string too long. Expected a string with maximum length 64, but got a string with length 1248 instead."}} (Request ID: 00000-497c26d0-b311-47dc-bb7f-510d85d85852)
### Steps to reproduce
Was chatting away in new app, creating a project and then fixing issues with it. Then just stops working and gives me:
Error: Session token expired and the request could not be retried. Please resend your message. (Request ID: F51D:1BA88C:D8DD96:E55194:6A21B1E3)
and then when I try to continue chat:
Error: Execution failed: CAPIError: 400 {"error":{"code":"bad_request","type":"websocket_error","message":"[ApiIdParam] [input[1].id] [string_above_max_length] Invalid 'input[1].id': string too long. Expected a string with maximum length 64, but got a string with length 1248 instead."}} (Request ID: 00000-497c26d0-b311-47dc-bb7f-510d85d85852)
So wasted 25% of my session limit, 9% of my weekly limit and however much of my PAID AI credits
### Expected behavior
For it to work and not fail part way through a chat - especially for a service I pay for!
### Additional context
_No response_
Contributor guide
Research direction
No source file, test, or entry point is named. Start by reproducing the failure on Windows 11 with v0.2.23, then trace the session-token expiry and websocket request associated with the maximum-length input[1].id error. Done means the project can continue after this failure without the reported request error.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100