Running into a weird edge case with the Node.js SDK (genesys-cloud/genesys-cloud-node v3.1.2). We’re cleaning up test tenants and I need to delete a user without nuking their historical interactions.
I’m using the standard delete flow:
const userApi = new PlatformClient.UsersApi();
await userApi.deleteUser(userId);
The API returns a 204 No Content immediately. But when I query /api/v2/analytics/interactions/summary later, the userId field in the response body still points to that deleted user’s ID. The user object itself is gone, but the historical data isn’t anonymized or reparented. It just hangs there referencing a ghost.
I tried calling POST /api/v2/users/{userId}/deactivate first, then deleting, but the result is the same. The docs mention a retention setting, but that seems to control when data is purged, not how it’s linked during deletion.
Is there a specific flag or a separate API call I’m missing to ensure interactions get scrubbed or reassigned before the user record is dropped? Or is this expected behavior and I have to handle the data cleaning on our side?