It would be really nice. You can step through flows and see the values of all the local variables as well as all the inputs/outputs of each block. It wouldn’t do any actions, it would just show what it did, basically like traces. The difference between this and traces is that it would show the values of all local variables in that moment.
I’ve considered breakpoint debugging, where you could add a breakpoint block that would stop flow execution, and you’d have the option to let it continue from a panel where you could basically see the “trace so far”.
Step-through debugging, requiring a “continue” press on each block, very likely won’t happen for a number of reasons. You could theoretically re-create that using breakpoints, but there are performance and usability reasons for why that shouldn’t be the default in my opinion (feel free to try and change my mind if you have a compelling use-case though).
Regardless of the exact UX, this won’t happen until async folders are redesigned, since it is dependent on the development of a new system that would allow flows to be spawned from existing state, and a system to serialize flow state more efficiently than the format used for traces.
I’ve added breakpoint debugging to Trello. https://trello.com/c/pQ1IMxDt/239-breakpoint-debugging
1 Like
I don’t think I explained it very well. It would be basically like flow traces, where you can click through and see inputs and outputs, but it would let you monitor the values of all local variables. Maybe instead of being a separate thing you could just add some sort of a display for local variables to traces?