Outlook email trigger node not starting with 1 minute pool time anymoer

[giuseppe_accardo]

I am on a self hosted release of [email protected], I have an Outlook trigger node with a pool time of one minute. It used to work till last release, now it doesn’t. it doesn’t even start at all. The connection with the microsfot account is correct and it is working as I can kick off the workflow manually with no problems.
I am on Windows 11 Home, 32 Gb of ram and a Omen 16 with a 5090 RTX.
Thank you
Giuseppe

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[not0lucky]

can you tell us more about the workflow? like the outlook trigger works when u get a new email? or every one minute is the trigger for the outlook?
Because the outlook trigger works when you receive a new email in general. Can you share a screenshot of the workflow to understand it more? thanks!

[giuseppe_accardo]

Hi thank you for gettting back to me so fast.

here is the set up for the Outlook trigger node. The account is correct and works fine.

I set it up in a way that every minute it checks for new unread emails.

Before the last update when I set the workflow to “Active” the cron job would kick and check for new emails with the chosen cadence and process the unread email(s).

Now whene I set the workflow to Active nothing happens.

However if I click on Execute Workflow it works just fine.

So something is not triggering the “one minute” kick off time for the cron job as far as I can tell.

This is the only thing that I can think of.

Let me know if u need more info.

I am going to check on a different system where I will transfer this workflow … but I do not think it will make any difference …

Thank you again for yuor time and patience.

Cheers

Giuseppe

[not0lucky]

Hi, I’ve been testing again but its weird since its already working when you execute it manually.
For the connection to outlook there’s no doubt its not working since the workflow is running well.
Did you try making a new working and try again with the trigger node and test it alone and see the output if its gets triggered. just to test alone.
Also do you check the execution tab in your workflow page, you can make sure that its working in the backend. and if there’s something wrong they will tell its an error while the workflow is active

[giuseppe_accardo]

Will do as you have suggested, will get back to you soon. Thank you

[giuseppe_accardo]

I did many tests … in short using Chrome fixed the problem. Not sure why but it worked till this am after the update on Firefox. I did run the workflow with Chrome and now is working just fine,.

Thank you for you support.

Much appreciated.

Giuseppe

[not0lucky]

Probably the browser plays a role in a day, I use brave browser and sometimes stuff doesnt work in it but when I switch to chrome it works perfectly fine.

Glad it worked for you!