As an example, here's what happened because I wasn...
# prefect-uis
Sam Gross
01/21/2025, 4:43 PMAs an example, here's what happened because I wasn't watching during the holiday. On the old page, you can tell things are stuck (and not failing/timing out properly, but that's my issue not yours). On the new page, you can only tell if you notice that the last successful job was a day or two ago.
k
Kevin Grismore
01/21/2025, 5:56 PMwhat does your Lateness tab say?
s
Sam Gross
01/21/2025, 5:56 PMI didn't know it existed!
Sam Gross
01/21/2025, 5:56 PMIt was off the side of my screen
Sam Gross
01/21/2025, 5:57 PMScreenshot 2025-01-21 at 12.57.06 PM.png
k
Kevin Grismore
01/21/2025, 5:58 PMwell that on its own is good feedback!
c
Craig Harshbarger
01/21/2025, 6:02 PMThis is good feedback for sure. The lateness metric should pick up on this sort of thing, because that number should start climbing if you run into this.
Also in the display menu you can sort the runs based on lateness as well. So that might help bubble late runs up to the surface.
s
Sam Gross
01/21/2025, 6:03 PMRight!
Sam Gross
01/21/2025, 6:03 PMBut all of that requires me to glance at it and know things are late
k
Kevin Grismore
01/21/2025, 6:05 PMis this just a tab visibility issue on smaller screens/windows?
s
Sam Gross
01/21/2025, 6:26 PMSomewhat? But I think also the presentation of the current state of the world is now less colorful (cleaner) but less glanceable
Sam Gross
01/21/2025, 6:26 PMYou need to read the UI (even if the tabs are visible) vs being able to instantly capture the state of your pipeline(s)
👍 1
Sam Gross
01/23/2025, 6:30 PMAh! I think I also see another issue that I didn't realize — the new Metrics Powered page only shows run state based on the returned success/failure value. All of our workflows were recently upgraded from 2.x -> 3.x and a bunch still don't return success. The old page shows success if you exit(0) and failure if you exit(1).
2 Views