- Genesys Cloud UK East
- ServiceNow Tokyo Release
- Architect Flow v4
Can anyone clarify why the /api/v2/conversations/{id} PUT request returns a 409 Conflict error when updating the custom attribute for ServiceNow ticket linkage? The payload includes the correct etag from the prior GET request, yet the conflict persists on every retry.