Darien Kindlund

@janober , can an n8n specify a workflow to be *globally* visible to *all* users and then make that one the default error workflow? Like, don't let other users alter...

Hey @Joffcom , `51595` was the execution ID of the running workflow. `51659` was the execution ID of an already successfully completed workflow. I haven't tried running the latest release...

Okay, it might a side-effect of a Chrome AdBlocker extension then... I'll retest on my end.. Thanks for the sanity check, @Joffcom

Okay, even with the extension disabled, I'm still seeing it for *long* running executions. @Joffcom , is it possible for you to re-test on your end and attempt to visit...

Okay, it looks like upgrading to v1.39.1 appears to have resolved this issue. Closing accordingly.

Side note btw, @marcklingen -- it would be great if the `prompts_get` endpoint supported like an optional param of `version=latest` so that you didn't have to constantly update those numbers...

Hey @Joffcom , this might be a regression but I'm encountering the same issue on [email protected] as well. Specifically, when a scheduled workflow is running, and I try to manually...

Hey @Joffcom , when I press stop, the UI briefly changes the workflow to a "stopped" state, but then during the next auto-refresh, it goes back to "running". I'm not...

Hey @Joffcom , that's a good question. I don't have it running locally -- it's deployed as a Google Cloud Run container. It's currently configured to spin up between 1...

Hey @Joffcom , it occurred to me that I never got a reply back to my original architecture question posted in the community forum about this issue: https://community.n8n.io/t/n8n-architecture-questions/40375 Specifically, is...