Choose the folders that belong in the product
Message delta operates per folder. Discover folders, store their Graph IDs, and maintain separate state for Inbox, Sent Items, custom folders, or shared mailbox folders selected by the product.
Graph delta provides durable folder-level change tracking when the client treats next and delta links as opaque state and pairs notifications with reconciliation.
Message delta operates per folder. Discover folders, store their Graph IDs, and maintain separate state for Inbox, Sent Items, custom folders, or shared mailbox folders selected by the product.
Begin at the folder's messages/delta endpoint, apply each page, and follow the exact @odata.nextLink until Graph returns @odata.deltaLink. An interrupted round must resume from its saved next link or restart safely.
Replay the stored delta link, upsert current messages, process removal markers, and commit the new link only after the changes succeed. Keep provider change keys for conditional updates where the workflow writes back.
Change notifications can wake the folder worker, but subscriptions expire and notification delivery is not the local source of truth. Renew before expiry, validate notifications, and run delta after gaps or lifecycle warnings.
That is the provider's documented message change boundary. A product that synchronizes several folders must coordinate several independent delta streams.
No. Delta query reconciles the authoritative set of additions, updates, and deletions; the notification is primarily a trigger to perform that work promptly.
Not yet. Gmail, Microsoft Graph, and IMAP/SMTP connectors are planned. This guide documents the intended architecture and the provider requirements a production release must satisfy.
DewEngine is in development. Real use cases decide what ships first.