Approve deletion of a saved search

In Complexity, select your mailbox and request deletion of a saved search. deleteOwnSavedSearch needs mail.savedSearches.delete and a MailGen license. It also needs an available finder permission, a group grant, and tool selection.

The tool proposes deletion. Its completed output stores the owned definition's name, expression, ID, and full snapshot. Review the exact target on the browser approval card before confirming. The browser sends proposal identifiers only.

At approval, BFF checks current actor permissions, active mailbox, grant, and definition snapshot. One approval row binds the run and tool call. Its durable operationId becomes the request's requestId.

DataSearcher compares the full expected definition inside an owner-scoped transaction, deletes it, and stops its versions' runs. A changed snapshot returns a conflict and requires a new proposal.

The human DELETE /saved-searches/:id route still permits an optional expectedSnapshot. Agent approval always supplies it. After a BFF failure, retry with the same durable request ID returns the DataSearcher receipt. A different intent conflicts with the stored fingerprint.

This deletes the saved search definition and retires its runs. It does not delete email. See saved search tools.

The current browser approval path requires an active verified Microsoft mailbox binding. A Google login or mailbox does not satisfy that approval boundary.