DELETE /api/v2/users/{userId} returns 409 Conflict due to active interactions

I’m trying to clean up stale test users in our staging org, but the DELETE /api/v2/users/{userId} endpoint keeps failing with a 409 Conflict. The error message says the user has active interactions. I need to remove the user without nuking the historical WEM data we’ve been tracking for the last six months. Is there a specific sequence of API calls to detach these interactions before the delete request goes through?

haven’t tried the direct delete route in a while. usually, you just need to offboard the user first via POST /api/v2/users/{userId}/offboard. that clears active sessions. once offboarded, the delete endpoint should work without conflict. worth a shot before digging into interaction detachment logic.