Hi :wave: Sorry for bringing this up here again, ...
# ask-community
y
Hi 👋 Sorry for bringing this up here again, as there is already a Git issue opened. I just fear that this will fall through the cracks. This is a huge chunk of functionality that has completely disappeared, and our daily routine with Prefect mainly involved checking this UI, which is now missing. Can someone from the DEV team confirm this issue and provide some ETA for the fix? @Deceivious @nicholas Thank you for any help on the issue. 🙏 https://github.com/PrefectHQ/prefect/issues/9485
👀 2
d
It usually takes 1-3 days to get Prefect team to get tickets off the triage tag.
y
Got it. Is there any way of getting this expedited?
d
Unsure. Hope some one from Prefect deems the issue to be High priority. But I am guessing itll be a low priority. 😄
y
I really hope this won’t be deemed as low priority. Maybe I am missing something, but this completely breaks the way we used to work with the UI.
d
I think the server is backwards compatible. So you can always spin up a UI and API only server with v2.10.6
while keeping the orchestrator @ 2.10.7
y
Yeah, this might be a solution, but I doubt we’ll find time to set this up.
We are completely reliant on Prefect Cloud.
d
Ah if its prefect cloud then thats not possible
n
Hi folks - thanks for the pings and for opening a ticket. Can you help me understand how you were using that chart? That’ll help the team prioritize internally
d
We basically lost observability. Prior to the update we could go to the flows page and see the status of last few runs of each of the flow in a single page. Now we have to apply filters one by one for each flow and if you have 100s of flow thats a major issue.
n
Got it, that’s helpful context, thank you
I’ll chat with the team a bit and see what we can do to bring that (or equivalent) functionality back
y
@nicholas I’ll also try to explain the need. You have 100 deployments. All of them are scheduled with a CRON expression. In the old screen, you could just quickly scroll down the page and make sure that each deployment has GREEN bars that are evenly spaced. Meaning, if one of those flows runs 1 time each month, I could very clearly see that it run correctly for the last 10 months. If it wouldn’t run for a specific month, a green bar would be missing between the evenly spaced bars. Does it makes things clearer? If it would help, I would happily go on a quick Zoom to explain this.
n
No that’s exactly the type of use I was looking for - thanks @Yaron Levi
y
Yes (-: I am still trying to understand how this entire thing was just cut off 🙃 It’s not just a small dropdown or some filter box that went the buggy way. It’s a very important way of monitoring many Flows, and it’s weird to me how many have not complained yet. Maybe we are missing something? Maybe there is an alternative way to get the same view…
n
Tbh we hadn’t heard that it was being used for the sort of validation use case you have - it wasn’t a well-supported feature generally and views like the dashboard generally provide much more robust insight into problems
That said - I hear your use case, I’ll see what I can do
y
OK thanks! Please contact me if you need more context.
🙏 1