Why does Grok Bot say "An error occurred while classifying this action" with no approval card?
Last checked October 29, 2026 · Grok Bot changes often
On October 29, 2026 staff said the Auto-review error ("An error occurred while classifying this action. Please review manually.") was a temporary issue on their side that started shortly before a user upgraded to 0.78.1, not caused by the update. When the check errors, the action is blocked instead of being sent to you, and the approval retry runs the same check again. Retrying later should work as things recover. Turning Auto-review off also works, but reviewed actions then run without the check.
What it looks like
After a reviewed action such as launching a cloud agent, computer use, or some Shell commands, the tool returns "An error occured while classifying this action. Please review manually." No approval card appears in the chat, so there is nothing to click, and asking again returns the same error. Simple read-only commands sometimes still ran.
What staff said
- It was not caused by the 0.78.1 update. It started shortly before, affected other users, and spanned cloud agent launches, computer use and Shell.
- The missing card is how the check currently behaves on error: the action is blocked rather than sent to you for approval.
- The approval retry runs the same check, so it fails the same way. Staff called this a known issue.
- Nothing needs to change on your end.
What you can do
| Choice | Effect |
|---|---|
| Retry in a while | Should work once the check recovers |
| Turn Auto-review off in Settings | Bots keep working, but reviewed actions run without the check |
If you turn it off, turn it back on once errors stop. Do not do this for Bots that handle money, email sends or production access unless you accept that risk; see Is Grok Bot safe?.
A different cause for stalls is an approval card you have not clicked; see Bot failed to respond.
Not tested by Boterly
We have not reproduced this. The status can change quickly; check the linked thread for whether staff have marked it fixed.