Trying to auto-adjust predictive routing scorecard weights right at shift handover. The Studio flow grabs the current occupancy count, calculates a new multiplier, and pushes it through a REST Proxy endpoint hitting PATCH /api/v2/predictiverouting/scorecards/{id}. Step one: the SNIPPET action builds the JSON payload with the updated value field and sets the header to application/json. Step two: the proxy forwards the request, but the response comes back with a 400 Bad Request. Body looks like {"code": "PREDICTIVE_ROUTING_INVALID_WEIGHT", "message": "Scorecard weight must align with configured scaling rules."}. The math checks out. Multiplier sits at 1.05. Console logs show the payload formatting perfectly. Switched to a basic HTTP request action just to bypass the proxy layer, same error. PR engine doesn’t seem to like hot updates while a campaign is actively routing. Queue monitor just sits there doing jack all while the script loops. London timezone offset might be messing with the shift window validation. Step three: checked the scaling parameter against the scorecard definition. It matches exactly. Still getting the 400. API docs mention something about campaign state locks, but it’s nowhere near a hard limit. Payload looks like this: {"value": 1.05, "scaling": "linear"}.