n8n - 💡(How to fix) Fix Outlook trigger, folders to include buggy. some folders work, some dont? [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28969Fetched 2026-04-24 06:12:59
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

Using microsoft outlook trigger, with option folders to include does not seem to work in production. In editor test events it pulls the correct emails, but in production does not.

To Reproduce

Grab a microsoft outlook trigger node. Make 2 folders in outlook, and put some maisl in them. enable to folders to inlcude, and include those 2 folders. Test fetch event in editor should work, en pulls the mails that are in there. but when publishing it, it wont return the same effect as in the editor.

Expected behavior

If i test fetch an event in the editor, and the mails pull up, it should also trigger these mails in production.

But the odd thing is, in a different older project, already has been published for a while. it does work. but no clue why, so I dont want to touch it.

<img width="767" height="1048" alt="Image" src="https://github.com/user-attachments/assets/c9bf6409-a194-4f69-b3fd-7caf63cbeba2" />

This currently does pull all the mails at the cron moments in production.

and in a different project, I believe it only grabs 2/3 random folders out of the 20 folders it has in its array.. So I'm a little overwhelmed about the whole outlook trigger node so I cant give a specifik pattern about these.

Debug Info

Debug info

core

  • n8nVersion: 2.17.5
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 5
  • license: enterprise (sandbox)
  • consumerId: 00000000-0000-0000-0000-000000000000

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 2500 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64; rv:150.0) gecko/20100101 firefox/150.0
  • isTouchDevice: false

Generated at: 2026-04-23T09:53:13.045Z

Operating System

windows 11

n8n Version

2.17.5

Node.js Version

24.14.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The Microsoft Outlook trigger node may not be correctly configured or authenticated in production, causing it to not fetch emails as expected.

Guidance

  • Verify that the Outlook trigger node is properly configured with the correct credentials and folder settings in production.
  • Check the n8n cloud logs for any error messages related to the Outlook trigger node to identify potential authentication or connection issues.
  • Compare the configuration of the working older project with the current project to identify any differences that might be causing the issue.
  • Test the Outlook trigger node with a single folder to include, to see if the issue is related to the number of folders being fetched.

Example

No code snippet is provided as the issue seems to be related to configuration and authentication.

Notes

The issue might be related to the differences in configuration between the editor and production environments, or authentication issues with the Outlook API.

Recommendation

Apply workaround: Verify and adjust the Outlook trigger node configuration and authentication settings in production to match the working older project, and test with a single folder to include.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

If i test fetch an event in the editor, and the mails pull up, it should also trigger these mails in production.

But the odd thing is, in a different older project, already has been published for a while. it does work. but no clue why, so I dont want to touch it.

<img width="767" height="1048" alt="Image" src="https://github.com/user-attachments/assets/c9bf6409-a194-4f69-b3fd-7caf63cbeba2" />

This currently does pull all the mails at the cron moments in production.

and in a different project, I believe it only grabs 2/3 random folders out of the 20 folders it has in its array.. So I'm a little overwhelmed about the whole outlook trigger node so I cant give a specifik pattern about these.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING