The above agent that I see in Prefect Cloud is never coming back online. At what point will the Cloud automatically "remove" remembrance of this agent? I ask because I could conceivably name agents for purposes of tying them back to transient local resources in which case the number of named agents that are never coming back would get very large... clicking "remove" on all of them would be a nightmare.

I wish the home screen included a widget showing recent runs (it shows only failed runs and runs in progress)

I wish the Runs screen (under a given flow) showed late runs too (it shows only runs that have run or are running, not those that haven’t yet run)

I wish the Runs screen (under a given flow) let me customize the columns, or at least added a few columns, especially on wide monitors - virtually the entire display width tells me about time (scheduled start time, actual start time, end time, duration) - I don’t care much about all those things, and care more about things like “label”, “current task” (for running flows), etc

Hi, I have an opinion that can improve UI / UX. It would be great if on the calendar tab, you could select multiple Flow (possibly projects) to look at the intersection of past Flow launches. How difficult is it to implement, are there any pitfalls that I do not see?

Hi - I noticed a minor UI bug where the new

run config

subtab bumps the links out of the box.

Hi! I have a question, when I schedule something in the UI it says "The Perfect Scheduler will only schedule 10 runs in advance", I am not sure why is it like that and what should I do if I wanted to, let's say, schedule flows for an entire month (must I do it from the code?)

Minor bug: Misaligned line in Flows page

Hi all, I see that the UI search bar successfully lets me pull up flow runs, tasks and task runs by their ID (I just copy/paste the GUID), but this is not working for flows. I can look up flows by name, however. Is this intended, that I cannot look up a flow by ID, a transient issue or a bug?

Hi everyone! Why the ui doesn’t logout after a certain Session lifetime? Is there a way to activate it ?

Is there a way to set the Prefect Run Configuration default in the UI? Of not, how do I do it on registration. I need to specify a Local config rather than Universal for some jobs.

I wish I could resize the columns and/or change which columns are displayed, on Flow > Runs page - we put a lot of run meta data in our flow run names, and not being able to see the full name (on a 13" laptop monitor) is ever so slightly annoying

I wish the flow name was as wide as the viewport allowed it to be - we use long flow names sometimes (maybe we are weird?) and seeing them truncated, with a bunch of white space to the right, is 😿 - details in thread…

Hi, Is it normal that my runs are reinitialized ? I don’t see any historic

This message was deleted.

Hey everyone, I can't get agent automations in prefect cloud to work. When I setup an agent automation, it asks me to create or choose an agent config. I tried to pass on the name of this config to my agent on startup with the

--agent-config-id

flag, however that does not work because the

prefect agent docker start

command expects that flag to contain an id. Can anyone help me with that?

Hello 👋 question. I have a mapped task with 8 runs in it. 2/8 tasks are hung (the dask-workers aren’t responding anymore) but I don’t want to cancel the entire flow and re-run it. What is supposed to happen when I set the task state of these 2/8 to Resume? They are then automatically progressed to Submitted. but never picked up by a worker for execution?

Hello everyone 👋. QQ: Is there a way to enable multi-user and project management features in the core/open source UI version? Thinking of something self-hosted...

Hi! The UI doesn't seem to agree with CRON (or me, or the code-based schedules). I've managed to create a task with a schedule

*/5 * * */2 *

which the UI correctly parses as

Every 5 minutes, every 2 months

. However, I can't set that schedule in the UI, is that by design or an unintentional discrepancy between the two? The same input under Settings -> Schedule -> Advanced -> Cron just tells me "Invalid Input" :(

Hello ladies and gentlemen, I run prefect local agent on one machine and use prefect cloud as backend. When I execute flow - agent creates child process which executes my flow. If this child process is killed for some reason (g.e. my Unix supervisor kills it for OOM) agent just retrying as configured, got the same result and give up. In web UI I can see that my task has 'running' status but it's actually do nothing. It's definitely a problem cause you can't really understand where your tasks are running or killed. I would expect agent collects info about killed child process and inform backed so I could at least see something is wrong with agent. Is this problem solved or maybe I can fix it somehow ?

#bug-ui Under a certain window width (about this much), the navigation ribbon that is meant to be under the blue section at the top does not display. This is a significant impediment to functionality if I put the cloud UI on my secondary monitor.

Is it possible to keep the agents fixed in position? they keep moving around after 10 seconds..

Just wanted to point out that on the dashboard, the tabs for running/submitted flows are swapped:

Also, I am having some terrible UI performance now that I am testing with a more full workload, the number of projects / flows (55 projects with 27 registered flows each) I have deployed just cause terrible slowness

Is there a way I can make these logs more space efficient? Each line of logs takes up so much screen space that I have to scroll quite a lot to read through the logs.

Hi All, question regarding logs in the prefect UI. We mostly use the RunNamespacedJob Task with the option log_level='info' to make sure the logs also show in the prefect logs. This worked fine in version 0.14.10. Recently we upgraded to 0.15.3 and I'm noticing that the logs don't show up in the prefect ui anymore. The logs do show up in the prefect-flow pod. Any idea how to fix this?

Is there a bug going around for the task-run schematic page not updating? On our's it shows all tasks as pending yet the flow is absolutely running and the logs show that. It just started for us (last 40 minutes). Prefect version 0.15.7 and we're using the prefect-cloud.

Sorry if this isn’t the appropriate place. I’m seeing some odd behavior in Prefect Cloud where one of my flows is duplicated in the project list. Mostly want to make sure I’m not doing something wrong on my end that is contributing to this: