Daniel Katz

    Daniel Katz

    10 months ago
    Another question 🙂 is it possible to have the following constraint: Schedule "flow a" to run every 10 minutes & prevent scheduling "flow a" if there is an existing invocation still running.
    Kevin Kho

    Kevin Kho

    10 months ago
    For Cloud, we have Flow Run Concurrency. For server, I have this code snippet from another Server user.
    It gets all the flow runs of the flow and sees if there are still ongoing ones. This state handler is then attached to the Flow
    Daniel Katz

    Daniel Katz

    10 months ago
    perfect, thank you!
    My team is very much enjoying Prefect so far, mostly thanks to your amazing community response time!
    Kevin Kho

    Kevin Kho

    10 months ago
    Thank you! 🙂
    Kevin Mullins

    Kevin Mullins

    10 months ago
    For Prefect Cloud, with the concurrency based off the flow run config labels, does this mean that an agent has to be configured with specific labels to limit flows? For instance, say I have
    source1-database-extract
    and
    source2-database-extract
    flows that each flow should only have a single instance per source to prevent issues. Does this mean I have to add tags for every flow to the agent to ensure they can run only once per source?
    Kevin Kho

    Kevin Kho

    10 months ago
    Yes but flow labels just need to be a subset of agent labels of if you have a label for
    source1
    and another for
    source2
    , the agent can pick both up if it has both the labels. And then yes you would apply the concurrency limit on the
    source1
    label and on the
    source2
    label
    Kevin Mullins

    Kevin Mullins

    10 months ago
    Ok, thanks for the clarification!