Did inbox automation miss an email? Reconcile the mailbox and work queue
Check whether mailbox messages reached your work queue after missed notifications, with an Outlook example and a practical acceptance test.
When an enquiry is visible in Outlook but absent from your task queue, compare the mailbox records with the intake records before restarting the automation. Give each eligible message a confirmed destination or an explicit exception. A working notification connection alone cannot prove that the gap is closed. This guide explains how a small agency can specify and test that comparison without turning every rediscovered message into another reply.
Separate notification delivery from enquiry intake
An email notification tells an integration that something changed. Your business still needs evidence that the relevant message was inspected, matched to a case and assigned a next action. Croissant recommends keeping those milestones separate in the operating view. A notification is the kitchen bell; the order still needs a ticket.
Microsoft documents that slow or unresponsive Microsoft Graph webhook endpoints can have notifications dropped. Some dropped notifications cannot be recovered. That describes the notification delivery mechanism; it does not establish that the underlying email was deleted. Ask the implementer how the workflow finds mailbox records when a notification never reaches it. [1]
The decision here is whether intake is complete. For choosing categories and routing ordinary messages, use our shared inbox triage guide. For this check, start with the source mailbox and compare it with the work your team can actually see.
Define the mailbox coverage before counting gaps
Write down the mailbox, included folders, eligibility rules and comparison interval. An enquiry moved into a separate sales folder should not vanish from the agreed scope merely because somebody tidied the Inbox. Excluded newsletters and automatic replies need a documented rule so they do not become unexplained missing tasks.
Microsoft Graph message delta queries track additions, changes and deletions in a folder. Tracking a folder hierarchy requires tracking each folder individually. A completed round returns a delta link for the next round; intermediate next links indicate that more pages remain. These are Graph-specific mechanics, rather than a promise that every Outlook connector exposes them. [2]
Ask the supplier to show how its actual connector covers the agreed folders and completes pagination. If it cannot demonstrate that coverage, describe the check as partial. Choose a supported manual comparison or a different scoped design before accepting a claim that all enquiries are covered.
Build a small comparison record
For each eligible source message, retain a restricted reference, the time it was observed, the associated case or task identifier and the latest confirmed disposition. Useful dispositions include linked to an existing case, new review item created, excluded under an agreed rule, and unresolved. Keep message bodies out of broad alerts; authorized colleagues can follow the protected source link.
Require the implementer to demonstrate how message identity survives the moves and retries used by your workflow. Subject text alone is an unsafe matching rule: two people can ask the same question. A conversation can also contain several messages that belong to one case. Compare both message coverage and case linkage instead of expecting equal mailbox and task counts.
Keep the last completed source comparison separate from the latest notification time. A fresh notification does not explain an earlier gap. Advance the comparison checkpoint only when the connector has durably accounted for the retrieved records, including visible exceptions. These are Croissant acceptance recommendations; the storage and transaction design depends on the integration.
Worked example: three messages arrive during a quiet failure
This is a synthetic test for a fictional agency, not a customer incident. During an agreed test interval, messages M-101, M-102 and M-103 reach an included mailbox folder while notification delivery is interrupted. The test uses harmless messages and a non-sending workflow. An authorized colleague manually handles M-101 and records its existing case C-21 before recovery begins.
After the connection is restored, the source comparison finds all three messages. It links M-101 to C-21 without creating another task. M-102 is a new eligible enquiry, so it creates one review item with a source reference. M-103 belongs to an existing conversation whose destination is uncertain; it remains an exception for a person to resolve. The catch-up process sends no automatic response.
The first pass has accounted for three source messages, but business intake is still incomplete because M-103 is unresolved. The owner checks the destination and links it to the correct existing case. The comparison can then report three messages accounted for, with two existing case links and one new review item. Those numbers describe this example only.
Run the comparison again over the same test material. It should preserve the same case links and create no additional review items. This second pass tests recovery behavior, not just discovery. Our duplicate prevention guide explains how uncertain destination actions should remain visible until they are reconciled.
Ask for evidence of notification recovery too
Microsoft Graph offers lifecycle notifications for reauthorization, subscription removal and missed notifications. Microsoft describes using synchronization, such as delta queries, to identify missed changes after recreating a removed subscription. Ask which of these signals the proposed integration supports and who responds to them. Lifecycle support is specific to the subscribed resource and implementation. [3]
Treat connection repair and backlog reconciliation as separate acceptance items. The technical owner confirms that the supported connection is working. The operations owner confirms that eligible messages from the affected coverage interval have a destination or a named exception. A green connection badge closes neither item by itself.
If a saved synchronization state is rejected, let the authorized technical owner use the provider's supported recovery procedure. Do not invent a new checkpoint at the current time and call the gap resolved. Keep the affected period visible until the team can explain the coverage it recovered and any limits that remain.
Keep the catch-up lane under human control
Reconciliation discovers work; it should not silently authorize customer commitments. An old message may have been answered manually, superseded by another conversation or withdrawn. During recovery, route newly discovered enquiries to review until the owner checks that a reply is still appropriate. Preserve the normal approval rules for quotes, contracts and start dates.
This method cannot prove coverage for mail the integration was never permitted to read or records that are no longer available. Record those limits explicitly. If the evidence is incomplete, keep the result unresolved and give the operations owner a bounded manual check. Broader permissions should not be an automatic response to a gap.
Before commissioning a build, ask to see this acceptance test in the actual connector alongside the inbox workflow demo. To discuss a scoped implementation, bring Croissant one intake workflow, its included folders and a fictional failure example. Leave credentials and private customer messages out of the brief.
Implementation checklist
- List the included mailbox folders and eligibility rules.
- Show the last completed source comparison separately from notification activity.
- Demonstrate full pagination and durable handling before checkpoint advancement.
- Link eligible messages to cases or explicit exceptions using tested identity rules.
- Test missed notifications with synthetic messages in a non-sending workflow.
- Include a manually handled message and an uncertain destination in the test.
- Repeat the comparison and verify that no duplicate work is created.
- Assign unresolved gaps to an owner and preserve ordinary reply approvals.
The sources behind the sauce.
Primary research and official documentation behind the cited points. The workflow examples and checklists are Croissant’s own guidance.