Trying to understand why updating participant attributes mid-call triggers a conflict when the call is active. I am using the Python SDK to push external CRM data into the conversation context via a PATCH request to /api/v2/conversations/voice/{conversation_id}/participants/{participant_id}. The payload includes attributes as a nested object, but the API consistently returns HTTP 409 Conflict with the message Resource conflict. The documentation states attributes are mutable, yet the SDK raises a GenesysCloudApiException every time I attempt this while the leg is ringing or connected. How do I correctly merge external attributes into a live voice participant without triggering a version conflict?