Intermittent auth error on manual execution / activation: “No authorization information present on the request.”
Hi everyone! Posting this as per Jon’s request, just to document and track a recurring issue I’ve encountered. I’m not actively looking for solutions unless someone has already seen this and knows a fix or workaround — mainly hoping to see if others have experienced the same.
I’m seeing an intermittent issue when testing a working orchestration workflow that uses Outlook and Teams (Microsoft 365) inputs. Everything runs fine for a while, and then—often after editing some non‑Teams nodes or simply taking a short break—the next manual execution (or clicking Activate) fails with:
Problem running workflow
Operation: Create
Execution: [Status Code: Forbidden; Reason: No authorization information present on the request.]
All credentials have been stable and in active use for 1+ month. The error clears only after a sequence of saves/refreshes or an admin-side restart.
What I’m doing
- Manual test executions via Outlook & Teams triggers/actions (Microsoft 365).
- Occasionally tweak unrelated nodes (not Teams-related), or leave the editor idle for a few minutes.
- Return and manually execute again or click Activate.
What I expect
- Manual execution and activation should work consistently without re-auth prompts or forbidden errors, since credentials are valid and previously working.
What actually happens
- Manual execution fails immediately with the error above.
- Clicking Activate sometimes triggers the same error.
- After a save/refresh cycle (and occasionally a workflow restart from the admin panel), the exact same manual Teams trigger run succeeds as if nothing was wrong.
Frequency
Has appeared several times over the last few days of testing, even when no relevant workflow changes were made.
Steps to reproduce (as best as I can tell)
- Open a known-working workflow that uses Outlook/Teams nodes and valid Microsoft credentials.
- Run a manual execution — it succeeds.
- Edit some unrelated nodes (non-Teams), or leave the editor idle for a few minutes.
- Run another manual execution or click Activate.
- Observe the error:
Forbidden; No authorization information present on the request. - Perform Save → Refresh (sometimes works). If not, Save → Refresh → Restart workflow (admin panel) → Refresh (usually clears it).
Troubleshooting attempted
- Verified credentials are still connected and unchanged.
- Re-auth was not requested by n8n.
- Save → Refresh resolves intermittently; Save → Refresh → Admin restart → Refresh resolves more reliably.
- After clearing, the same Teams manual trigger run works normally.
Additional context
This feels like some transient credential/session context getting lost between edits/idle periods, since a simple editor Save/Refresh or workflow restart temporarily restores normal behavior.
Due to client confidentiality, I’m unable to share the full workflow publicly, but happy to provide logs or isolated node details if needed.
Questions for the community
- Has anyone seen Microsoft 365/Teams nodes intermittently lose auth context during manual runs or on activation?
- Are there known timeouts or token refresh edge cases in the editor that could explain this?
- Any logs/metrics you recommend enabling to catch the exact moment auth context is dropped?
Thanks in advance for any pointers or if there’s a known fix/workaround I can apply!
Information on your n8n setup
- n8n version: 1.110.1 (Latest Stable)
- Database (default: SQLite): N/A
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
- Operating system: MacOS Sequoia 15.6.1