“OpenClaw change was cancelled because its run ended”: the approval card, explained
A cancelled approval could be a bug in OpenClaw 2026.9.1, fixed in 2026.9.2. How to check the version and distinguish the bug from a stopped or expired request.
If an OpenClaw configuration approval disappears with “OpenClaw change was cancelled because its run ended,” check the running version first. The failure happens on 2026.9.1; the fix shipped in 2026.9.2. Update to a release containing that fix, then request the change again. Replying faster is not a reliable repair: the old flow could record an Allow without applying the change.
The approval could fail even when you clicked Allow
A configuration proposal is not the configuration change itself. OpenClaw asks for permission, then has to apply the approved operation. On 2026.9.1, over Telegram, both halves can fail: a proposal is cancelled when the requesting turn ends, and an approval card can accept Allow yet leave the requested settings unchanged. Nothing tells the owner that the approved change has not happened.
That matches the upstream delegated-approval fix: the requesting tool now waits for application or a terminal result such as denial, cancellation or expiry. An accepted permission decision and a completed write are no longer reported as if they were interchangeable.
Check the version, then make a fresh request
openclaw --versionRun this where the agent runs. For a container, check inside the running container; a newer CLI elsewhere says nothing about the Gateway handling your chat. Follow the update procedure for your installation if it is still on 2026.9.1.
After updating, ask for a new proposal and review that proposal’s requested change. A cancelled link is not revived by clicking it again. Check the actual setting afterwards: for a configuration path, use openclaw config get <path> or the relevant settings page. The agent saying it changed something is not the check.
When cancellation is still expected
The fix does not remove approval boundaries. Stopping the requesting run still cancels its proposal, expired approvals stay expired, and a late Allow cannot authorize a write for a closed run. In the upstream fix’s tests the approval window was ten minutes, so on 2026.9.1 a card that disappears after a few seconds is not simply using up that window.
If a fresh proposal still fails on an updated Gateway without you stopping the run, keep the exact error, version and channel when reporting it. Do not disable approval protection to make a broken proposal work.
A changed default can leave the current chat unchanged
A model-default change can apply while the conversation keeps its session-specific model choice, which is a different outcome from the missing write. If the setting reads correctly but replies still use the previous model, check the conversation’s model override; for reasoning effort, check the chat’s thinking-level setting.