Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Outlook trigger filter query does not work in production. [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#28963•Fetched 2026-04-24 06:13:04
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
ThomasVottThomasVott
Participants
n8n-assistant[bot]n8n-assistant[bot]ThomasVottThomasVott
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

When using outlook trigger, using the filter option. and have it set to this filter: not(categories/any(c:c eq 'AI-Queue')) and not(categories/any(c:c eq 'AI-Processed')) and not(categories/any(c:c eq 'AI-Review-Required'))

In editor/test it does work, it pulls the expected mails when fetching test event. When published, it does not pull anything.

To Reproduce

<img width="615" height="661" alt="Image" src="https://github.com/user-attachments/assets/bed78b22-2125-4058-b42b-da987ebffdfb" />

Grab a Outlook trigger, turn on Filter Query, Add this filter in there: not(categories/any(c:c eq 'AI-Queue')) and not(categories/any(c:c eq 'AI-Processed')) and not(categories/any(c:c eq 'AI-Review-Required'))

Fetch test event > Should grab any mail thats in your mailbox, Production > Does not pull any mail at any time.

Expected behavior

Output of test/editor environment should be the same as production environment. So it should pull all the mails that does not contain the tags.

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:32:12.329Z

Operating System

windows 11

n8n Version

2.17.5

Node.js Version

nodeJsVersion: 24.14.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The Outlook trigger filter may not be working as expected in production due to differences in environment or configuration, and verifying the filter query and checking for any errors or warnings in the production logs may help resolve the issue.

Guidance

  • Verify that the filter query is correctly formatted and applied in the production environment, and check for any errors or warnings related to the filter query in the production logs.
  • Compare the test and production environments to identify any differences in configuration or setup that may be causing the discrepancy.
  • Check the n8n cloud documentation to see if there are any known issues or limitations with the Outlook trigger filter in production environments.
  • Test the filter query with a simplified condition to see if the issue is specific to the complex filter query.

Example

No code snippet is provided as the issue is related to configuration and environment differences.

Notes

The issue may be related to the differences in environment or configuration between the test and production setups, and further investigation is needed to identify the root cause.

Recommendation

Apply workaround: Verify and adjust the filter query and environment configuration to ensure consistency between test and production environments, as the issue may be related to differences in setup or configuration.

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

Output of test/editor environment should be the same as production environment. So it should pull all the mails that does not contain the tags.

#network issue#logging issue#authentication issue#prompt issue#agent setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Outlook trigger filter query does not work in production. [1 comments, 2 participants]