I’ve spent hours trying to figure out why updating a predictive routing strategy via the Platform API returns a 409 Conflict error. Our Premium App uses service account credentials with full admin scope. The payload matches the schema from the latest SDK docs, yet the conflict persists across multiple orgs. Rate limits are not being hit. What specific resource lock or versioning constraint causes this 409 response during strategy updates?