11:34Claude responded: "Microsoft 365 Watch Emails 404 error - item doesn't belong to targeted mailbox after connection change."Microsoft 365 Watch Emails 404 error - item doesn't belong to targeted mailbox after connection change."

:bullseye: What is your goal?

I want to connect claude to answer my FAQS in support emails

:thinking: What is the problem?

Hi, I’m hoping someone can help me resolve a persistent issue with my Make scenario.
My setup:

Watch Emails (Microsoft 365/Outlook) → Anthropic Claude → Send Email (Microsoft 365/Outlook)
The [email protected] mailbox is a dedicated Microsoft 365 Business Basic account
The scenario watches for incoming support emails, passes them to Claude for an AI reply, then sends the reply back to the sender

What works:

Claude reads the email perfectly and generates the correct JSON response
The Send Email module is correctly configured with the reply mapped to {{2.jsonResponse.replyEmail}}
The filter between Claude and Send Email correctly checks canAnswer: true

The problem:
After reconnecting the Microsoft 365 connection to the correct support mailbox, both the Watch Emails and Send Email modules return this error:
[404] Item ‘AAMkADdi…’ doesn’t belong to the targeted mailbox ‘adfe46d5-b8b1-4a7c-8a2a-4ad34ec44e4c’
I have tried:

Reauthorizing the connection
Using “Choose where to start” → “From now on”
Deleting and recreating the connection
The error keeps recurring and the Watch Emails module shows “no new data” even with unread emails in the inbox

Any help gratefully received!

:test_tube: What have you tried so far?

Here’s a summary you can paste in:

What we have tried:

Reconnected the Microsoft 365 connection multiple times using the correct [email protected] credentials
Deleted all old connections and created a fresh one
Reauthorized the connection in Credentials
Used “Choose where to start” with every option — All, From now on, Since specific date, and Choose manually (which showed “No data available”)
Changed Watch Emails from Only Unread to All Emails
Added a search filter to:[email protected] to isolate support emails
Cleared the search filter again
Changed the Mail Folder setting
Ran the scenario manually with Run once many times
Turned the scenario on to run automatically every 15 minutes
Sent multiple fresh test emails to the support inbox during testing

None of these resolved the 404 error. The Watch Emails module either returns “no new data” or the 404 “item doesn’t belong to targeted mailbox” error, even though the support inbox is confirmed to be receiving emails correctly.Sonnet 4.6 Low

Welcome to the Make community!

This is not a bug.

Polling Triggers & Empty “Check Runs”

This is because the module is a POLLING trigger, and not an INSTANT (Webhook) trigger.

If you don’t see any bundles from the trigger module and operations on the rest of the modules, it means there are no new responses (empty output bundle) when the scenario ran to check for new items. This is called a “Check run”.

There are two main types of triggers, Polling (scheduled), and Instant (webhooks). Polling triggers can only run on a schedule. Instant triggers can be run as soon as data is received by the webhook.

  • Polling means Make checks external service for changes (pull changes to Make).
  • Webhook (instant) triggers means external service calls Make when there are new changes (push changes to Make).

The module you are using does not push changes — it’s basically a API request that Make has to occasionally “call” to fetch the latest changes/items.

To find out more on the different types of Trigger modules, see refer to Types of Modules and Webhooks sections of the Make Help Centre.

If you want your scenario to only run when there is new data (and not on a schedule or timed interval), see if your app has an “Instant” or “Webhook” trigger in Make. If not, check if the third-party service has a feature that can send out a webhook when content is created/updated - and then you can point it to a “Custom Webhook” trigger in your scenario.

If you want to re-run your scenario on older data,

Polling Triggers: Selecting Older Data Using Epoch Panel

Go to the Epoch Panel, by right-clicking on the trigger module (polling triggers only), and select “Choose where to start” from the list of options in the context menu.

If you select “From now on”, the next time the scenario runs it will only return new data (or nothing if there is no new data).


Above: A screenshot of a polling trigger module’s Epoch Panel

You can also select other old data to re-run your scenario with next using the “Choose manually” option. This will then show you a list of previous historical items you can select to process the next time the scenario is triggered.

For more information, see

Hope this helps! If you are still having trouble, please provide more details.

@samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!