I’m completely stumped as to why the Genesys Cloud POST /api/v2/users endpoint returns a 409 Conflict with the message “User with this email already exists” when running our automated migration script from Zendesk Support. We are migrating approximately 2,000 agents, and the script handles email normalization by trimming whitespace and converting to lowercase before sending the request, which mirrors how Zendesk handles unique identifiers in their POST /api/v2/users endpoint. The error occurs specifically on the second pass of our retry logic, even though we verified via the GET /api/v2/users?email={email} endpoint that no user with that specific email exists in the target Genesys Cloud organization. The response body includes a X-Request-Id but no detailed conflict resolution hints. We are using the Genesys Cloud Python SDK version v2.15.0 and running the script from a server in the Europe/Paris timezone to match our business hours. In Zendesk, duplicate emails are often merged or flagged differently, but here it seems to treat any historical deletion or soft-delete as a permanent block. We have checked the “Archived Users” view in the Genesys Cloud admin portal, and the users in question do not appear there either. Is there a hidden cache or a delayed propagation issue with the email uniqueness constraint in the Platform API? We need a reliable way to either overwrite the existing record or retrieve the correct user ID to update their skills and routing profiles, similar to how we handled duplicate ticket mappings during the Zendesk migration. Any insights on bypassing this conflict or properly cleaning up residual user data would be appreciated.