Default or Current flow target used for builds

Thank you.  I grabbed the quote, to paste here.

"Multiple flow targets are also supported, in which case the build workspace gets the union of their contents. The only restriction is that there be no overlap between the targets' components. Such collisions can be avoided by configuring scoped flows in the workspace editor."

This is really good to keep in mind in configuring my build strategy.

However, now I'm thinking about the use case where a typical developer, not a release engineer, has multiple flow targets (for whatever reason) and they don't know about this behavior.

So, say a developer have 2 flow targets for his workspace, and they are not scoped, meaning that both flow targets include all components and they overlap.  They request a personal build, override the workspace configured for the build definition, and expect the build to take from their current flow target.  With overlapping components what will happen? 

Thanks.

they will get a warning message, and usually junk output from the build. (depending on the resulting conflicts of course). I don't know if there are any precedence rules on the order of which targets are used.  it might be sequential.

A personal build does not run an accept/replace, it just does the load of the given dev workspace.

doah, of course.. personal means use my workspace!..  sorry I missed that.