From f4d6f1a19debfd828f7743516a497e4fd444b8f7 Mon Sep 17 00:00:00 2001 From: Corie Watson Date: Tue, 10 Nov 2026 16:04:54 +0000 Subject: [PATCH] docs(delete-user-data): note that a failed event publish doesn't stop deletion Lists it under the README's differences from the extension, as the firestore-bigquery-export kit README does. Refs #3254. --- kits/delete-user-data/README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/kits/delete-user-data/README.md b/kits/delete-user-data/README.md index e53195ac1..70266b9f0 100644 --- a/kits/delete-user-data/README.md +++ b/kits/delete-user-data/README.md @@ -336,6 +336,13 @@ The Firebase CLI now sets it to the function that published the event so it differs between `clearData`, `handleSearch` and `handleDeletion`. If your event triggers filter on `source`, filter on the event `type` instead. +### A failed event publish doesn't stop deletion + +If an event can't be published, the kit logs a warning and carries on deleting. +The extension failed the function instead: in `clearData`, auto-discovery and +`SEARCH_FUNCTION` were skipped, so their data was left behind, and +`handleSearch` and `handleDeletion` failed after deleting. + ### Unchanged Event types and payloads are the same. The functions still publish