Skip to content

Commit 7d368aa

Browse files
Update user-deletion-and-suppression.md
added status and rephrased failed status sentence
1 parent 20b8c22 commit 7d368aa

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

src/privacy/user-deletion-and-suppression.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,16 @@ The deletion requests tab shows a log of all regulations with a deletion element
8484

8585
In the Segment App (Settings > End User Privacy > Deletion Requests), you can click a userId to view its status in Segment internal systems, and in the connected destinations.
8686

87-
When checking the status of deletion requests via the API, the deletion will report an overall status of all of the deletion processes. This means that, even if the deletion from Segment Internal Systems and supported destinations were completed successfully, the status can still be 'FAILED', due to a failure on a unsupported destination.
87+
The deletion request can have one of the following statuses:
88+
1. "FAILED"
89+
2. "FINISHED"
90+
3. "INITIALIZED"
91+
4. "INVALID"
92+
5. "NOT_SUPPORTED"
93+
6. "PARTIAL_SUCCESS"
94+
7. "RUNNING"
95+
96+
When checking the status of deletion requests via the API, the deletion will report an overall status of all of the deletion processes. As a result, we will return a 'FAILED' status because of a failure on a unsupported destination, even if the deletion from Segment Internal Systems and supported destinations were completed successfully.
8897

8998
### Regulate User from a single Source in a Workspace
9099

0 commit comments

Comments
 (0)