Several people saw this Auto-review error on October 29, 2026. Here's what they posted, what the status page showed, and what SpaceXSI's docs say to try.
All Grok Bot questions: https://www.soundminds.ai/faq.
Last updated Oct 30, 2026
On the evening of October 29, 2026, several people posted on X that Grok Bot's Auto-review was failing with "An error occurred while classifying this action." Their posts say it stopped Shell commands, routine saves and posting, and that no approval card showed up. Some of the posts spell it "occured."
The official status page listed an incident called Auto Review Degradation. It started at 7:44 PM ET on October 29 and was marked resolved at 9:20 PM ET. The status page doesn't mention this error message, so I can't say the incident caused every report. When I checked at 11:08 AM ET on October 30, the status page showed All Systems Operational.
SpaceXSI's docs don't list this message. The steps below are the general ones the docs give for service incidents and for errors, and none of them has been tested against this error.
Step 1: Check the status page. I checked SpaceXSI's Troubleshooting page, and it says, "Check status.cursor.com and look at the Grok Bot row." It also says, "If the status page shows a Grok Bot incident, wait for it to be resolved, then send your message again." I read the incident on status.x.ai, which is where status.cursor.com sends you, so it is the page the docs mean.
Step 2: Try the task again. The Troubleshooting page says, "Copy the request ID from the message, then try the task again." If the message doesn't show a request ID, that page says to include the error text and a screenshot instead when you report it.
Step 3: If it still fails, fully quit Grok Bot and reopen it. The Troubleshooting page says, "Most problems clear with a full restart: fully quit Grok Bot (on Mac, choose Quit from the menu bar, not just closing the window), reopen it, and try again before anything else."
Step 4: Don't reset the computer or reinstall the app for this. The Troubleshooting page says that when the status page shows a Grok Bot incident, "Don't Reset the computer or reinstall the app. Neither fixes a service problem, and Reset can lose very recent changes if the computer can't be reached to save them."
Step 5: If the same prompt fails on a fresh run, report it. The Troubleshooting page says to "report a bug and include the error text and request ID." On desktop, open the account menu and choose Support, then Send Feedback. The page also asks you to include your Grok Bot version and platform, the exact error message, and the approximate time and time zone.
If the error comes back after the status page says the incident is resolved, send feedback as in Step 5. One post I read, from Anshuman Bhartiya, is time-stamped 9:39 PM ET, which is after the 9:20 PM ET resolved update, and it says retries kept failing. So I can't say whether every account recovered at the same moment.
I'm not suggesting you turn Auto-review off. One person on X said it was the only thing that worked, and nothing in SpaceXSI's docs says that. SpaceXSI's Approvals, security, and privacy page says, "With Auto Review off, the Bot runs actions without checking them first, and your Custom Rules are hidden and not used but kept; turn it back on to use them again."
These are posts from people on X, not from SpaceXSI. Quotes are word for word, and I credit each person by the name their profile shows. Times are Eastern.
These are three people's own words. They describe different actions that failed: Shell commands and routine saves in one post, posting in another, and local-tool actions in the third. None of the three says what caused the error beyond calling it a bug or an outage. I haven't confirmed any of it myself.
I read the official status page's incident data on October 30, 2026. The data was last updated at 11:08 AM ET. It lists one incident for Auto Review, Auto Review Degradation. It names Grok Bot as the affected component and marks the impact as minor. It has two updates:
The incident lines up in time with the reports. The earliest of the October 29 posts, from nezquik, puts the start at about 7:38 PM ET, around six minutes before the first update. But the status page doesn't say what caused the incident, which actions it affected, or whether it involved the message "An error occurred while classifying this action." So I'm not saying the incident caused every report.
@grok, the AI account on X, also named this incident. At 9:30 PM ET on October 29, 2026, it replied to another user about a different error message, "Failed get_task_by_conversation_id_if_exists", and wrote that it "matches recent reports during the Auto Review Degradation." That is @grok's own wording and not SpaceXSI's status page, and it's about a different message, so I don't use its advice here.
A Cursor forum thread, Grok Bot Auto-review: classifying error, no approval card (0.78.1), was opened at 8:11 PM ET on October 28, 2026 about the same message. A reply from Colin, marked as Cursor staff, was posted at 5:11 AM ET on October 29, 2026. It says, "This wasn’t caused by the 0.78.1 update. It’s a temporary issue on our side with the Auto-review check" and "the action is blocked instead of being sent to you for approval, and the approval retry runs the same check again, so it fails the same way."
That reply came about 14 and a half hours before the status page incident, so it describes an earlier stretch of the same message. It is a forum reply and not SpaceXSI's docs, so I don't take any steps from it.
I read SpaceXSI's Troubleshooting page and its Approvals, security, and privacy page on October 30, 2026. Neither lists this error message. Neither says what to do when an Auto-review error shows no approval card, or whether approving again re-runs the same check. So I've left out anything about that rather than guess.
SpaceXSI docs, Troubleshooting: https://docs.x.ai/grok-bot/troubleshooting
Check status.cursor.com and look at the Grok Bot row.
If the status page shows a Grok Bot incident, wait for it to be resolved, then send your message again.
Don't Reset the computer or reinstall the app. Neither fixes a service problem, and Reset can lose very recent changes if the computer can't be reached to save them.
Most problems clear with a full restart: fully quit Grok Bot (on Mac, choose Quit from the menu bar, not just closing the window), reopen it, and try again before anything else.
Copy the request ID from the message, then try the task again.
If the menu doesn't offer it, that message has no request ID; include the error text and a screenshot instead.
SpaceXSI docs, Approvals, security, and privacy: https://docs.x.ai/grok-bot/approvals-security-and-privacy
With Auto Review off, the Bot runs actions without checking them first, and your Custom Rules are hidden and not used but kept; turn it back on to use them again.
Grok Bot status page, Auto Review Degradation (October 29, 2026): https://status.x.ai/history?incident=grok-bot%2Fps_e5eb22a9954466c4
We are investigating a degradation in Auto Review functionality
This has been resolved
nezquik (@x_nezquik) on X: https://x.com/x_nezquik/status/2115955346854617259
Mike Gannotti (@MichaelGannotti) on X: https://x.com/MichaelGannotti/status/2115958257152115000
Anshuman Bhartiya (@anshuman_bh) on X: https://x.com/anshuman_bh/status/2115981958669042159
Grok (@grok) on X: https://x.com/grok/status/2115979613289558322
Cursor forum, Auto-review classifying error thread: https://forum.cursor.com/t/grok-bot-auto-review-classifying-error-no-approval-card-0-78-1/176550
See how I set up Grok Bot: https://www.soundminds.ai/setup.