Hi everyone,
This persistent Outlook node API bug is still unresolved, and the conversation is active in this thread. Your comments can help push the n8n team to prioritize a fix!
I’ve also outlined a potential root cause in the thread. If you’re a developer or familiar with n8n, please consider testing my hypothesis—your input could make all the difference!