https://docs.all-hands.dev/ logo
Join Slack
Powered by
suddenly all my convos are stuck at `connecting`. ...
# proj-agent-canvas
w
suddenly all my convos are stuck at 
connecting
. I've only got 1 running right now, and did a full restart. No CPU/memory pressure Any ideas what would cause this?
events aren't flowing through at all. refresh eventually loads (but very slowly) and shows the new events
lots of requests stuck 
pending
after a refresh
backend logs during a refresh
Copy code
15:39:07 [agent-server] INFO     207.180.140.243:0 - "GET /server_info HTTP/1.1" 200
15:39:07 [agent-server] INFO     Settings accessed  settings_router.py:159
15:39:07 [agent-server] INFO     207.180.140.243:0 - "GET /api/settings HTTP/1.1" 200
15:39:07 [agent-server] INFO     207.180.140.243:0 - "GET /server_info HTTP/1.1" 200
15:39:07 [agent-server] INFO     207.180.140.243:0 - "GET /api/file/home HTTP/1.1" 200
15:39:08 [agent-server] INFO     207.180.140.243:0 - "GET /api/profiles HTTP/1.1" 200
15:39:08 [agent-server] INFO     207.180.140.243:0 - "GET /api/conversations?ids=c9bc27e5-280f-42c8-979f-d7fef3a6a72c HTTP/1.1" 200
15:39:08 [agent-server] INFO     207.180.140.243:0 - "GET /api/agent-profiles HTTP/1.1" 200
15:39:08 [agent-server] INFO     Settings accessed  settings_router.py:159
15:39:08 [agent-server] INFO     207.180.140.243:0 - "GET /api/settings HTTP/1.1" 200
15:39:08 [agent-server] INFO     207.180.140.243:0 - "GET /api/conversations?ids=f298c104-56ca-4491-a22c-c6361a604ff5 HTTP/1.1" 200
15:39:08 [agent-server] INFO     Loaded 5 skills  skills_service.py:430
15:39:08 [agent-server] INFO     207.180.140.243:0 - "POST /api/skills HTTP/1.1" 200
15:39:08 [automation] {"message": "207.180.140.243:0 - \"GET /api/automation/sdk-version HTTP/1.1\" 200", "severity": "INFO"}
15:39:08 [agent-server] INFO     207.180.140.243:0 - "WebSocket /sockets/bash-events" [accepted]  wsproto_impl.py:385
15:39:08 [agent-server] INFO     WebSocket authenticated via first-message auth  sockets.py:222
15:39:08 [agent-server] INFO     Bash Websocket Connected  sockets.py:422
15:39:08 [agent-server] INFO     Received bash request  sockets.py:451
15:39:08 [automation] {"message": "207.180.140.243:0 - \"POST /api/automation/v1/telemetry/consent HTTP/1.1\" 200", "severity": "INFO"}
15:39:08 [agent-server] INFO     207.180.140.243:0 - "GET /api/workspaces HTTP/1.1" 200
15:39:08 [agent-server] INFO     Settings accessed  settings_router.py:159
15:39:08 [agent-server] INFO     207.180.140.243:0 - "GET /api/settings HTTP/1.1" 200
15:39:08 [agent-server] INFO     207.180.140.243:0 - "GET /server_info HTTP/1.1" 200
15:39:08 [agent-server] INFO     207.180.140.243:0 - "GET /api/conversations/f298c104-56ca-4491-a22c-c6361a604ff5 HTTP/1.1" 200
15:39:09 [agent-server] INFO     Loaded 6 skills  skills_service.py:430
15:39:09 [agent-server] INFO     207.180.140.243:0 - "POST /api/skills HTTP/1.1" 200
15:39:09 [agent-server] INFO     207.180.140.243:0 - "GET /api/conversations/f298c104-56ca-4491-a22c-c6361a604ff5/events/search?limit=50&sort_order=TIMESTAMP_DESC HTTP/1.1" 200
15:39:10 [agent-server] INFO     207.180.140.243:0 - "WebSocket /sockets/events/f298c104-56ca-4491-a22c-c6361a604ff5?resend_mode=since&after_timestamp=2026-08-19T15%3A38%3A25.221585" [accepted]  wsproto_impl.py:385
15:39:10 [agent-server] INFO     WebSocket authenticated via first-message auth  sockets.py:222
15:39:10 [agent-server] INFO     Event Websocket Connected: f298c104-56ca-4491-a22c-c6361a604ff5  sockets.py:282
15:39:10 [agent-server] INFO     Settings accessed  settings_router.py:159
15:39:10 [agent-server] INFO     207.180.140.243:0 - "GET /api/settings HTTP/1.1" 200
15:39:10 [agent-server] INFO     207.180.140.243:0 - "GET /server_info HTTP/1.1" 200
15:39:11 [agent-server] INFO     Found 0 total git changes in /root/git/dj-station  git_changes.py:214
15:39:11 [agent-server] INFO     Resending events since 2026-08-19 15:38:25.221585: f298c104-56ca-4491-a22c-c6361a604ff5  sockets.py:337
15:39:11 [agent-server] INFO     207.180.140.243:0 - "GET /api/git/changes?path=%2Froot%2Fgit%2Fdj-station HTTP/1.1" 200
15:39:11 [agent-server] INFO     207.180.140.243:0 - "POST /api/bash/execute_bash_command HTTP/1.1" 200
15:39:11 [agent-server] INFO     207.180.140.243:0 - "GET /api/git/commits?path=%2Froot%2Fgit%2Fdj-station&limit=50 HTTP/1.1" 200
15:39:11 [agent-server] INFO     207.180.140.243:0 - "POST /api/bash/execute_bash_command HTTP/1.1" 200
15:39:11 [agent-server] INFO     207.180.140.243:0 - "POST /api/auth/workspace-session HTTP/1.1" 204
15:39:11 [agent-server] INFO     207.180.140.243:0 - "GET /api/file/search_subdirs?path=%2Froot%2Fgit HTTP/1.1" 200
15:39:12 [agent-server] INFO     207.180.140.243:0 - "GET /api/conversations/search?limit=20&sort_order=UPDATED_AT_DESC HTTP/1.1" 200
15:39:12 [agent-server] INFO     207.180.140.243:0 - "GET /api/conversations/search?limit=20&sort_order=UPDATED_AT_DESC HTTP/1.1" 200
15:39:12 [agent-server] INFO     Found 0 total git changes in /root/git/dj-station  git_changes.py:214
15:39:12 [agent-server] INFO     207.180.140.243:0 - "GET /api/git/changes?path=%2Froot%2Fgit%2Fdj-station HTTP/1.1" 200
h
Is this on 1.14 @wooden-umbrella-84098 ?
w
nod
it seems to have mostly recovered, but still feels v slow
I'm on a semi-bad internet connection but zoom is working fine and no performance issues noticed on other websites
h
I had a weird spike like that but it seemed to resolve itself after I tried digging in. It has a react memory leak smell but I couldn't find anything at the time. Those tend to go away magically on their own with browser closing/refreshing
a
(I also felt like it has been slow, but didn't try to quantify where the issue is happening)
w
noticing the agent keeps re-searching recent events every few seconds thonk
it's taking ~minutes to connect to the websocket
h
@millions-afternoon-47582 any ideas on what we might be able to look into here?
👀 1
m
The root cause may be that the events WebSocket lifecycle is tightly coupled to a REST query that triggers aggressive refetching.
w
Here's an agent's analysis of my HAR file
Untitled
Untitled
I'm gonna have my agent open a PR but would love for someone else to take it over the line
m
I’ll continue working on this issue and take it over the line once the PR is open. Thank you very much! thankyou
🙏 1
w
my agent died sadblob
can't recover the convo
but you can probably use the summary above as a starting point for a new agent
m
Yes, I’ll create a pull request based on the summary you provided. Thank you very much! thankyou
2 Views
Open in Slack
PreviousNext
Powered by