PATCH /conversations/participants fails with 409 Conflict on attribute update

Sending a PATCH to /api/v2/conversations/participants/{participantId} to update custom attributes returns a 409 Conflict. The payload is minimal:

{"attributes": {"priority": "high"}}

Tried including the if-match header from the initial GET, same error. Is there a specific lock behavior I’m missing here?