Feedback on new UI. This was spurred on by feedback provided here (which I agree with). Apologies for not having a video but I can't present anything meaningful without sharing sensitive work info. Looking at the flow run page, you have to select the current flow run on the LHS pane to get information about it displayed on the RHS.From the layout it seems that the Flow Run itself (including parameter values, when/where it ran, etc) are on the "same level" as individual task runs, log items, and events. I find it unnatural that the flow run information is not on it's own, always visible, element in the flow run page. When I'm trying to debug flows often times I need to look at the logs (Spark job error for example) then go back to the flow run parameter values and work with those 2 pieces of information in-tandem to figure out what the problem is. Since the logs on the LHS are not formatted properly, I use the RHS pane to look at the error, then shift back to the flow run item, then back to the error, etc. My feedback would be to: 1. Extract the flow run information to it's own pane that's more prominent, maybe even always visible (maybe next to the timeline?) 2. Properly format the logs in the LHS pane. This would basically mean that you never need to go the RHS pane to see log info and debugging.

@Jacob Blanco thanks for the feedback! #1 makes sense, thanks for sharing that. For #2 about the logs in the left what about them isn't properly formatted? If you could show an example of the left vs right and how they're formatted that would be helpful.

So I'm thinking specifically about Python stack traces. You can see on the right that the indentations and line-breaks are properly rendered so it's easier to parse what's happening. To my eyes this is not the case on the left.

Ahhhh that is an excellent piece of feedback. Let me see if we can fix the indentation on the left view 👍

oooh let me take a look! Thank you

Nice! Thanks for pointing the formatting out 👍

Complaining is easy, fixing is hard.