Event deletion is asynchronous and runs during non-peak hours — on PostHog Cloud typically over the weekend; a 200 response only means the deletion was queued.
You must delete by person UUID, not distinct_id.
Avoid reusing a deleted distinct_id before deletion fully processes — the new user can get mixed into the pending deletion; use the 'Reset deleted person' tool after processing completes.
This is a destructive, irreversible operation; confirm the person UUID and project before sending.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?