Request reconciliation of your mailbox

In Complexity, select an owned, verified, ACTIVE Microsoft mailbox and enable requestOwnMailboxReconciliation. The tool retains the administrative requirement admin.groups.manage, plus MailGen license, tool grant, and chat selection. Complete Graph setup first.

The strict input is empty. The model cannot choose another mailbox, source, recovery/reset mode, or subscription. The action requests existing folder/message delta and master-category reconciliation.

BFF submits actor-ordered mailbox.sync.reconciliation.request with a deterministic operation ID. Queue-only POST /sync/reconciliation-request accepts only a verified internal request and stored envelope. Execution rechecks current grant, license, permission, and exact actor/account/chat/run/tool binding. Prisma and unsupported providers create no Graph trigger.

The outbox keeps the same intent on retry. Published entries do not return to PENDING. The Graph trigger uses a separate deterministic UUID namespace from the command operation. Its correlation ID points to the original command. This prevents graphsync.apply from replacing the original operation.

GraphPullPoller durably deduplicates terminal and coalesced trigger replays. Coalesced acknowledgment and cycle update share one transaction and roll back together.

The first receipt has status: queued, syncCompleted: false, operation/correlation IDs, and fixed sources mail_folders_delta, folder_messages_delta, and master_categories. A separate request ID becomes available in the confirmed command receipt. That confirmation proves trigger persistence, not completed source synchronization. Use sync read tools or Sync Center for later status.

This differs from session-bound POST /api/connected-accounts/sync, which refreshes account metadata. It changes no login token/session ownership, mailbox selection, onboarding, disconnect, or subscription capability.