Answer
If a command inside a view/command group behaves differently across environments despite an apparently identical configuration, try removing the problematic command from the group and manually re-adding (dragging in) a working version of it, rather than trusting that the promoted configuration is actually equivalent — this has resolved cases where a command group carried some inconsistent or stale state that wasn't obviously visible in its configuration.