Saw version 2 drop on GitHub and decided to spin up a test instance. Spent some time digging through it and honestly... three of my workflows broke immediately. Not writing this to hype anything, just sharing what I found so maybe you don't have to troubleshoot this yourself when you upgrade.
The saves are instant now. That one second pause from version one? Just gone. You hit save and it's done before you even lift your finger. They also flattened the UI... nodes lost their white outlines, connectors are thicker and pop out when you hover, and there are these circular loading animations on slow nodes. Takes about ten minutes to adjust, but after that you barely notice. The side panels and general layout are still the same, so you're not relearning anything.
Publishing works differently and honestly it feels like more clicks. The activate toggle is gone. Now you publish with a version name, which is nice in theory, but unpublishing means digging into settings and clicking through menus. What used to be one click is now three or four. I couldn't find a way to link specific versions to public URLs either... maybe that's coming in the official release, but right now it just feels incomplete.
Here's what actually broke my stuff. Execute Workflow nodes work completely differently now. In version one, when you triggered a sub workflow, it would run and finish, but the data you originally passed in would come back unchanged. The sub workflow did its thing in isolation. In version two, whatever data gets created or modified inside that sub workflow now flows back to your main workflow automatically. So if your main workflow is waiting on a sub workflow to process something, you'll actually get that processed data back instead of just your original input. This caught me off guard because I had workflows built around the old behavior where sub workflows were essentially fire and forget. But here's the thing... this actually fixes a real pain point I've had with approval workflows. Before, getting human input back from a sub workflow into the parent required setting up separate webhooks or checking databases. Now the sub workflow can just wait for someone to approve or reject something, and that response flows back naturally so the main workflow can continue based on what actually happened.
Should you upgrade? Not if you have complex Execute Workflow setups in production or can't afford downtime. Maybe if you want to test the new behavior in a safe environment. I'm keeping production on version one and rebuilding my logic in a test instance first. The instant saves are tempting, but I'd rather spend some time testing than wake up to broken automations. This is still pre release... things might change. If you're using sub workflows, budget real time to test before upgrading. That's it.
