# Taking longer than expected in almost every Grok run **URL:** \ **Category:** Bug Reports\ **Tags:** performance, chat, grok\ **Created:** [August 27, 2026, 10:21am UTC](https://forum.cursor.com/t/taking-longer-than-expected-in-almost-every-grok-run/169673 "2026-08-27T10:21:09Z")\ **Posts on this page:** 1\ **Showing post:** 30
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 14, 2026, 9:37am UTC](https://forum.cursor.com/t/taking-longer-than-expected-in-almost-every-grok-run/169673/30 "2026-09-14T09:37:34Z")
Hey @thibauld, thanks for the request IDs, they were exactly what we needed. None of the three requests ever reached our servers. The message got stuck inside Cursor on your machine before it was sent, which is why nothing came back and why restarting was the only thing that helped. I would suggest upgrading to _v3.20_ to check if the issue persists. If so, please start a new thread! This thread was started during some heavy load on the model side at the end of August. To avoid this becoming a catch-all thread, I’m going to close it. --- _[View the full topic](https://forum.cursor.com/t/taking-longer-than-expected-in-almost-every-grok-run/169673)._