Can anyone clarify the exact behavior of the DELETE endpoint for users when we need to maintain referential integrity for past interactions? We are building a cleanup script using the Python SDK to remove dormant accounts, but the documentation is vague on whether deleting a user via genesyscloud.users.delete_user(user_id) automatically nullifies the routing.user fields in historical conversation records or if those links persist as dangling references.
response = client.users_api.delete_user(
user_id="abc-123",
cascade=True
)
Our concern is that if the user object is gone, our analytics dashboard throws errors when trying to fetch the user profile for conversations from six months ago. We want to soft delete or anonymize the user data without breaking the conversation lineage. Should we be updating the user’s routing.skills and routing.email_addresses to empty arrays before deletion, or is there a specific cascade flag that handles this differently? We need a programmatic way to ensure that GET /api/v2/conversations/{id} still returns valid metadata even after the associated user is removed from the directory.