fix: remove messages.queue.byProvider rejected by OpenClaw 2026.1.29 #34
+0
−19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
messages.queue.byProviderfrom generated config — upstream schema no longer accepts this key as of OpenClaw 2026.1.29routing.queue.byProvideroption definition from both instance and top-level module optionsrouting.queue.mode(still valid upstream) is preservedUsers needing per-channel queue overrides can use
configOverrides:Test plan
nix flake check --no-buildpassesbyProviderin moduleFixes #33
🤖 Generated with Claude Code