@Marvin Is there any way to prevent flows from being executed from the UI?

Yes, you can restrict the ability to execute flows from the Prefect UI by managing user permissions. From the documentation on user roles and permissions (source: https://docs.prefect.io/latest/cloud/users/roles/): You can configure roles that define what actions a user can take, such as executing flows, creating deployments, or viewing flow runs. To prevent users from executing flows via the UI, do not grant them the "Run deployments" or "Run flows" permissions in their role setting. If you're using Prefect Cloud, you need to create or modify roles accordingly and assign users to these roles. This ensures that only authorized users can run flows. For more granular control, you can also use the Prefect Client to interact with the API and manage permissions programmatically: https://docs.prefect.io/latest/guides/using-the-client/ Let me know if you need more details on how to set up these roles or permissions.

@Marvin What if I want to prevent people from running a specific flow at all in the UI?

To prevent a specific flow from being executed via the UI, you could use the following strategies: 1. Manage User Permissions: Adjust permissions so that only specific users can execute flows. This can be managed in Prefect Cloud by configuring user roles and permissions. See the documentation here: https://docs.prefect.io/latest/cloud/users/roles/ 2. Cancel Pending Flow Runs: You can programmatically cancel flow runs using the Prefect Client API. This involves setting the state of a flow run to "Cancelled" to ensure it doesn't execute. Here's a sample script:

from prefect import get_client
from prefect.states import Cancelled

async def cancel_flow_run(flow_run_id):
    async with get_client() as client:
        await client.set_flow_run_state(flow_run_id, Cancelled())

3. Use Concurrency Limits: Set concurrency limits for the specific flow so that the flow runs don't get executed until resources become available. This can make the flow appear to be "hung" or delayed indefinitely. More information can be found here: https://docs.prefect.io/latest/guides/using-the-client/ By utilizing these strategies, you can effectively prevent specific flows from being executed from the UI. If further customization is needed, feel free to delve deeper into the Client API or explore Prefect's extensive documentation. For more detailed control: Prefect Client Guide If you encounter any issues, you may also refer to the relevant GitHub issues: - Prevent running late runs after some threshold - Increase visibility around maxed out concurrency limits Let me know if you need further assistance!