I reproduced this locally on current main.
The direct gateway approval RPC path works. The approval request is created, resolve with allow-once succeeds, and waitDecision returns allow-once.
The provider chat flow reproduces the issue. The approval is shown as pending and resolve with allow-once succeeds, but the later waitDecision call fails with INVALID_REQUEST: approval expired or not found.
The command still finishes afterward and smoke appears through the follow-up run. So the visible result can look successful, while the gateway still logs the failed waitDecision.
I only tested current main locally in this run.
#approval smoke
1 messages Β· Page 1 of 1 (latest)
ok cool - if you can try using telegram too just to validate it breaks there too
Is a shaped local repro ok for u ?
Telegram-shaped local test also reproduces it.
Turn source was telegram, resolve with allow-once succeeded, then waitDecision failed with INVALID_REQUEST: approval expired or not found.
Smoke still appeared afterward through the follow-up path.
Thank you
Hope it could help u.
what is ur github @?
to credit you and say thanks for the help testing :)
@timid sapphire when we fix ^^ would be nice :)
my clanker is saying https://github.com/openclaw/openclaw/pull/83433 seems like the cleaner fix!
Sounds good - let me test it with slack, discord and webui to validate
Thx for the Credit on fix. Can i close this since Fix is done ?