We currently use

version_group_id

when we register flows to differentiate the environment (i.e. prod, staging, etc). Not only do they run in separate environments, those flows all have separate version history as well. I see in the docs that

version_group_id

is deprecated. So what’s the best practice for differentiating flow groups for separate environments? Should we use the env as part of the flow name, e.g.

my_flow_prod

? And if that’s the case, does Project + Name uniquely identify the flow? Thanks!

As for your 2nd question, yes a project + flow name uniquely identifies a flow, so grouping by project may also work for your use case. Note that if you're using

Local

storage you'll need to explicitly specify a path (since the default path doesn't take the project into a ccount), but other than that things will work fine.

(that linked thread above has some other ideas for how to version flows between environments you may be interested in)