UserWarning: A flow with the same name is already contained in storage; if you changed your Flow since the last build, you might experience unexpected issues and should re-create your storage object.
 serialized_flow = flow.serialize(build=build) # type: Any
Flow URL: <https://cloud.prefect.io/XXX/flow/ZZZ>
 └── ID: XXXX
 └── Project: test_proj_2
 └── Labels: ['dev']

Hey y'all I am running flows in multiple projects but all the flows have the same name and same storage (by design, i don't wish to change the name). However when I register the flow to several projects I get this warning every time I call

flow.register(project_name)

(with different metadata of course like schedule time, etc) on a different project. I want to know what that warning means . Since I have the flows setup in production I want to know that if I update the flow metadata for one project is it going to do the other flows dirty ?

all the flows have the same name

This is not allowed, flow name must be unique across a project

Sorry I meant I have a flow with the same flow name under different projects

what storage do you use?

Github

it looks like the warning is useful and warns you that you may be overriding storage of one flow by a flow with the same name but from a different project

I am okay with all flows having the same storage but while registering I register them with a different schedule (which is metadat ofc that cloud picks up) to different projects. Is it okay ?

I know you said you wish to reuse the same flow name across different project, but I would highly encourage you to change that strategy. The flow names usually identify a flow and keeping the same name (and the same storage) for multiple flows across projects may bite you at some point.

Is it just parameter values and schedules that differ across projects?

Yes you are spot on ! I will surely explain more, I had gone away for a while ... in a meeting.

I see. If there is really nothing else that differs across flows than the parameter values and schedule, then this solution should work, provided that you set the parameter defaults and schedules using either the UI or GraphQL API: you can see below the same flow in project p and xyz but with different parameter defaults set through UI

Hey thanks @Anna Geller I'll read up on that - default parameters things and get back to you in a while. Point to note: I need to also think how do I keep track of the all the flow runs of a particular pipeline. For instance if it was a separate project then I would have a flow ID and it would just be a matter of getting all the flow runs of that ID . Like at least we may need to query like average time that the last 5 runs have taken, etc etc. ALSO for now I am not too sure if I really need all that information. .So yeah..I'll think about and see ya ! On a slight tangent , why don't use DARK MODE 😡 ?

@Tilak Maddy this should be doable with GraphQL, the duration or run statistics would either way have to be calculated through flow runs and task runs, not flows. You would then probably put your flow name and project name into the where conditions There is an experimental dark mode you can toggle here

Hey i use dark mode, i was just wondering why you weren't 😛 Not really angry - I am terrible emoji user (always fail to communicate the right thing)

I don’t spend that much time in the UI so normal white screen doesn’t bother me at all there tbh 🙂