#Agent never responds after restart

1 messages · Page 1 of 1 (latest)

night vigil
#

My agent never responds again after restarting it's like it forgets? It used to respond like let's say I say can you restart and let me know once it's done it will restart but it won't let me know it's done till I nudge it again... I'm sure it never use to do this I'm using gpt 5.4 and openclaw version 2026.4.15

half sandalBOT
whole idolBOT
#

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

lone mesaBOT
#

That sounds more like the post-restart wake is failing, not the agent truly forgetting.

A useful distinction here:

  • Session/state should survive restarts
  • The current in-flight reply does not
  • After restart, OpenClaw is supposed to send a separate wake/reply

So there are 2 likely cases:

  1. It restarted via plain exec / bash / external service command
    Then there is no guaranteed “I’m back” follow-up.

  2. It restarted via the built-in gateway restart/config/update path
    Then you should get a post-restart wake.

Also, if you’re using /restart specifically, that restart path does not preserve the interrupted reply, so what you’re seeing is pretty consistent with that.

#

Can you reproduce it once and paste:

openclaw status --all
openclaw logs --follow

Then trigger the restart and look for:

  • Restart sentinel present
  • gateway/restart-sentinel
  • outbound delivery failed

If you want one extra check after reproducing: