You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docs: clarify completion and cleanup for singular delete_user on the legacy route #252
Could the legacy Python SDK document the completion and cleanup guarantees for singular delete_user? This affects what an existing integration can safely record when an account deletion returns successfully or the response is lost.
The Python interface describes this method as synchronous and its implementation calls DELETE /users/{user_id}. The plural delete_users calls a separate endpoint and has a documented task workflow. In the JavaScript SDK v9.5.1, the response type for the same singular route includes an optional task_id. That type alone does not establish when the server returns one.
What has finished on a successful response without a task ID? If a task ID is returned, which work does it cover and should the caller poll it?
Does mark_messages_deleted=True preserve or erase message content and attachments? Which conversation channels are affected? Please identify any cleanup of uploaded files or Video data that requires a separate operation.
After a transport timeout, is there an authoritative read-only confirmation for this exact request, or a documented safe retry? In particular, what does a matching user.deleted event establish about completion of the requested cleanup?
A short note in the method documentation pointing existing callers to the applicable server contract or supported replacement would help. This request is based on the published interfaces. We have not performed a deletion to test these questions.
Activity