WFM API 409 Conflict during ServiceNow Quality Review Sync

Why does this setting trigger a 409?

Background

Syncing WFM quality reviews to ServiceNow via GitHub Actions. Using GC CLI v2023.10.0.

Issue

API returns 409 Conflict on PUT /api/v2/wfm/quality/evaluations. Error: Resource version mismatch.

Troubleshooting

Payload includes resource_version from GET. Verified timestamp alignment. The conflict persists despite correct concurrency headers. Is there a hidden lock mechanism in WFM analytics endpoints?