This topic was automatically generated from Slack. You can find the original thread here.
Another potential bug in the microsoft_outlook server. This makes the server not usable unfortunately. It would be great if you could prioritise this:
Hi , thank you for reaching out.
The original issue is closed. Could you kindly create a new bug issue instead?
Any chance you looked into it already? I think it’s a fairly trivial fix and it would make the server usable.
Hey , thanks for reminding me. I’ve added to Pipedream prioritized backlog. Our Component dev will take a look at it soon
Thanks for picking it up. I can’t seem to make it work. I wrote my findings here: [BUG] microsoft_outlook-find-email tool broken ascending/descending filter · Issue #17487 · PipedreamHQ/pipedream · GitHub
Would be great to look into it.
As noted in the action:
When you specify $filter, the service infers a sort order for the results. If you use both $orderby and $filter to get messages, because the server always infers a sort order for the results of a $filter, you must specify properties in certain ways
The certain ways are:
- Properties that appear in
$orderbymust also appear in$filter. - Properties that appear in
$orderbyare in the same order as in$filter. - Properties that are present in
$orderbyappear in$filterbefore any properties that aren’t.
Here’s an example (image below):
• Filter:receivedDateTime ge 2025-07-01 and inferenceClassification eq 'focused'
• Order By:receivedDateTime desc
Could you also test this without an explicit date? So to just sort on latest but with filter inferenceClassification eq ‘focused’?
Because we just want the latest emails in that folder or does it only work if we set a date?