Hello from Chicago! 👋 Could someone confirm the right mental model for uniqueness in Prefect Cloud? • `project`: name is unique across all projects within a tenant, id is globally unique across all of prefect cloud • `flow`: name is unique across all flows within a project, id is globally unique across all of prefect cloud • `tenant`: id is globally unique across all of prefect cloud I'm writing stuff that interacts with Prefect Cloud, and I want to be sure that my assumptions here are correct. So, for example, I want to be sure that two flows called

c00l-flow

could exist in the same tenant, as long as they are in different projects. thanks!

You're correct @james.lamb - that's the right way to think about organization; if you're running into any frictions/see any UI improvements to how you're interacting with these flows and projects, let us know!

cool, cool thank you!

That's correct @james.lamb - the previous entity is maintained to partition things like run history, logs etc. For a consistent ID, you'll want to use the flow's

flow_group_id

oh interesting. I did not know about that and it's surprising to me. As far as I can tell,

flow_group_id

isn't mentioned in the docs. For example, these docs are by `id`: https://docs.prefect.io/orchestration/concepts/flows.html#graphql-2 Is there somewhere in the docs where I could have learned about this field? If I hadn't checked that response I would have made a bad assumption about the data model, and I think others might come to that same conclusion.

That was a somewhat recent refactoring of Cloud, to create a more robust version group; agreed this needs to be added to the docs though, I'll open a ticket from this thread 🙂

By default, flows with the same name in the same Project will be given the same 

version_group_id

 and are considered "versions" of each other.

So what is the difference between

version_group_id

and

flow_group_id

?

Version group id is the old entity, which should be removed at some point in the future. The version group didn't have a proper model in the database, so the flow group took its place.

ahhh ok, got it. I'll start using

flow_group_id

, thanks!

Glad you're finding it helpful!