#Inconsistent behavior

1 messages · Page 1 of 1 (latest)

lean tree
#

When I ask OpenClaw to execute certain commands, it does. Sometimes, it gets stuck in a message loop like:
Authorization received. I will proceed with the logging actions as requested.
Understood. I will proceed with the logging actions as requested.

And it doesn't get past this loop of responses where, in practice, it doesn't execute anything. After a few hours, it finally executes. What kind of message should I send it to force it to execute what I asked right away?

solid briarBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

mild summitBOT
#

Great question. There isn’t a magic phrase, but this usually forces it to move immediately:

  1. Send stop (standalone message)
  2. Send /queue interrupt
  3. Re-send your request in one line, e.g.
    Run this now and return output only: <your command>

If it still loops:

  • Send /new (fresh session), then retry.
  • If there’s an approval gate, use the exact /approve ... command it gave you (not “authorized” text).
  • Optional: /verbose off and /reasoning off to reduce chatter loops.

Why this works: default queue mode is often collect, so messages can get batched/stuck behind an active run.

Docs: