A couple of suggestions about the Prefect 2.0 UI 1- In a scenario where the flow has a required input, If we go to the Deployments page and just click Run the job fails, saying that it is missing a parameter. In my opinion, if a parameter is required from the flow, it should not be possible to run a flow without informing the value. 2- It would be nice to change the default value from the deployment over the tab `Parameters`; that feels more natural than clicking on the three dots. 3 - On the work Queues section: would it be possible to check which agents are on? 4a - Over the Flow Runs, would be interesting to show on which “Work Queue” the task was executed. 4b - It would be nice to see the previous runs for each “Work Queue”, showing which Flow was executed on the given queue. 5 - Notification: Is it possible to add a notification when an agent/queue is off? (or when doesn’t have any agent waiting for upcoming requests for a given work queue). 6 - On the JSON Block, would be possible to show a history of modifications? Would be nice to easily identified when a modification was made with a diff showing the changes.

Thanks for the great suggestions. We will definitely consider about these suggestions. Here are some thoughts on 3 of your suggestions: 4a. You can see which flow is being executed in a work queue by clicking a work queue 5. Yes you can schedule when the agent is off. The flow just doesn’t run on schedule if the agent is not there

Hi @William Jamir - thanks for the ideas. If it's ok with you I'm going to move this into an issue so we can track your suggestions and make sure they don't get lost. For your #1 - there is some work happening right now to address that but we want to make sure we get the balance between reminders and restrictions right.

For #5 - I think you're asking for something that tells you when your agent isn't polling? We don't have that but adding a notification for when a run with the same tags is ‘Late’ will let you know there's an issue.

Hey @William Jamir, For 1., I would add -> Being able to create a storage block (staging area) where to put file trigger or file input to automaticaly start a flow which will process the file. With a specific agent or something like that. But I think that's why there is all the Cloud API... 😛

Thanks for the quick response @Khuyen Tran ! About point 3: Perhaps I expressed myself wrongly (I did not fully grasp the difference between an agent and Work Queue) 🙂 Assuming a scenario where I have two “Work Queues,”

test1

and

test2

. My suggestion is that each “Work Queue” should have a status indicating if there is “someone” ready to consume upcoming requests or not. Something similar on Prefect 1.0 would be enough, where a green line and a gray line helped to distinguish this information. (image attached) About point 4a. Actually ( prefect 2.0.2), you can only see “Upcoming Tasks”, my suggestion was to add information about where a tasks was executed (regardless of the run state). About 5. My suggestion was about enabling the user to create a notification related to “Work Queue”, for example, when there isn’t any “Agent” (I don’t know if this is the correct term) available to consume the upcoming tasks.

If the work queue Test1 doesn't have anyone available to consume upcoming tasks, send a notification to Slack
If the work queue Test1 has more than 1000 tasks, send a notification to Slack

If you wouldn't mind that would be great! You’re right that slack doesn’t keep messages for too long and the extra details are always helpful.