Outlook trigger fixed to retry missed messages
The Microsoft Outlook trigger node will now retry messages that arrived during failed API calls instead of skipping them permanently.
The Microsoft Outlook trigger node for n8n had a problem: when an API call failed mid-poll, any messages that arrived during that failed window would be skipped forever. The catch block in the poll method was missing a return statement, causing execution to fall through and advance the timestamp anyway. Add one line—return null—to preserve the timestamp when errors occur, and those messages get picked up on the next poll cycle.
This matters for automation workflows relying on the Outlook trigger. Without this fix, silent message loss could break downstream automations with no indication anything went wrong. The fix is in the n8n node-base package, targeting the Microsoft Outlook integration.
View Original GitHub Description
Summary
The poll() method's catch block was missing a return null statement. When an API call failed in trigger mode with an existing lastTimeChecked, execution fell through to advance lastTimeChecked = endDate, permanently skipping any messages that arrived during the failed poll window. Adding return null in the catch block preserves the previous timestamp so those messages are retried on the next poll cycle.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-4721
Review / Merge checklist
- PR title and summary are descriptive. (conventions)
- Docs updated or follow-up ticket created.
- Tests included.
- PR Labeled with
release/backport(if the PR is an urgent fix that needs to be backported)