Grok 4.7 requests stalled in Cursor this morning, staff say
Some Grok 4.7 runs hung or never answered from 2:20 to 3:50 AM ET, and slowness returned near 7:45 AM ET. Switch models if it hits you.
If Grok 4.7 in Cursor sits on "Taking longer than expected…" or ends a turn without replying, pick a different model in the model picker and resend. Cursor staff confirmed that "From about 06:20 to 07:50 UTC today, some Grok 4.7 requests (with or without Fast) were very slow to start or never got a response at all," and that they were "seeing some of the same slowness again around 11:45 UTC."
- Window: about 2:20 to 3:50 AM ET, then slowness again near 7:45 AM ET.
- Symptoms: slow starts, no reply at all, or a turn that ends right after a tool result.
- Fast mode: affected too ("with or without Fast").
- Status page: no incident listed when we checked at 10:23 AM ET.
What changed#
Yesterday Colin traced a different Grok 4.7 slowdown to "extra waiting on our side between the steps of a run." This morning he said that one "has been fixed since yesterday evening (UTC)," and that today's stall is a separate issue.
A second thread shows the same window from another angle. IliasKarim reported agent turns that stopped after a tool returned the answer, until a follow-up like ?? brought the reply. mohitjain replied at 9:54 AM ET that it "was an issue on our side with Grok 4.7 between roughly 06:20 and 07:50 UTC today" and has "been back to normal since then."
Why it matters#
If you run Grok 4.7 in Cursor, a turn that looks finished but never answered is easy to miss, especially on a long task you left running.
How to use it#
- If a Grok 4.7 turn hangs or stops without a reply, send a short follow-up first. That restarted stuck turns in this window.
- Still stuck? Switch to another model in the model picker and resend.
- Copy the Request ID from the chat's … menu (Copy > Copy Request ID) and add it to the forum thread so staff can check your requests.
Good to know#
- Colin said staff looked up one reporter's account directly; mohitjain still asks for a Request ID if it happens again.
- These reports come from Cursor's editor. We have no staff word on Grok Bot chats.
- A separate post at 9:35 AM ET shows Grok 4.7 repeating one word at a time in its thinking. At 1:02 PM ET, kevinn (Cursor staff) replied that "Grok 4.7 got stuck generating that text for several minutes at a time without taking any action, and it fell back into the same pattern after each retry," that it's "not caused by anything on your end," and that the team has been told. His advice: hit Stop right away, then start a new chat, lower the effort level to High, or switch models for that step. He didn't say whether it's the same problem as the morning stalls.
What to watch#
Whether the 7:45 AM ET slowness clears for good, and whether Cursor posts it on its status page.
