Workflow executes successfully, but execution data/UI is invisible (Can't map variables)

Questions
1

Hey everyone,
I’m currently running into a frustrating bug and would really appreciate your help.
The Problem:
About 8 out of 10 times when I execute my workflow, the automation actually runs and successfully completes its job in the background. However, the execution is completely “invisible” in the n8n editor.
The Impact:
Because the UI doesn’t show the output data after the run, I can’t see the results. More importantly, this means I can’t select or drag-and-drop any variables to set up my subsequent nodes. It completely blocks me from building and managing the next steps of my workflow.
Additional Info: Im using Safari on a McBook Air 2025 and right now the free n8n Trial.
Has anyone experienced this UI/execution sync issue or knows a workaround to make the node outputs visible again?
Thanks in advance for any ideas!

1 Like
2

This is almost certainly a Safari thing, Safari’s Intelligent Tracking Prevention causes session/auth weirdness with n8n and a bunch of users have reported similar issues where the workflow runs fine but the UI doesn’t sync up properly. Try Chrome or Firefox for your n8n work, or if you want to stick with Safari try it in Private Browsing mode which bypasses some of those restrictions. Your execution data is probably still being captured, you can check the Executions tab to confirm, it’s just not displaying inline in the editor.

3

Welcome to the community @Ben7

Safari can sometimes have issues with WebSocket connections (which n8n uses for real-time updates):

  • Test in Chrome or Firefox

  • If it works there, it confirms a Safari-specific issue

  • You can continue building in Chrome and use Safari for other tasks

Let me know what you find when you try a different browser’

4

Hi @Ben7 Welcome to the community!

This is pretty strange although i would recommend if you want to see your workflow running consider unpublishing your workflow and then try running it even if that does not show up just restart your n8n instance as most of the times it works, also i recommend when testing workflows do not use published flows as it is hard to actually map the issue even in the executions section, for now try unpublishing your workflow, and also keep your n8n instance updated to the latest stable version! Cheers!