#Reported bug closed
1 messages · Page 1 of 1 (latest)
I checked the issue. It was closed by clawsweeper[bot] because it matched an already-merged fix on main, not because your report was invalid.
The bot points to PR #81849, which fixes Telegram /stop getting stuck behind an active prompt lane. The important bit: that fix was on main only at the time, and the bot explicitly said no release tag contained it yet. So if you’re on 2025.5.12 / the affected release, you can still hit it until the next release includes that PR.
Relevant links:
https://github.com/openclaw/openclaw/issues/81938#issuecomment-4455186142
https://github.com/openclaw/openclaw/pull/81849
If you keep seeing it after updating to a release newer than the one containing #81849, that’s worth filing/reopening with the new openclaw --version and fresh logs.