The error happens when count is outside the bounds of autoscaling min/max. I created an issue for this, it should be disabling autoscaling when you run scale count manually.
The weird output is probably related. When you run the scale command it actually does the equivalent of a deploy. It’s likely conflicting with autoscaling and giving back weird errors.