technical question - two codebases on same Lucee server have this.name in Application.cfc set to same value, can it cause trouble for Lucee to locate CFCs? E.g. /model here and /model there with different set of CFCs

Yes. Typically the application name is unique ... https://www.bennadel.com/blog/1845-making-sure-your-coldfusion-applications-are-uniquely-named.htm

if you are running in single mode (green admin), there is only one name space for applications, but each request starts up with it's own runtime application config, if you are running multi-mode (red and blue admin) then the application namespace is per context. this is why you can modify the application settings during a request without affecting any other requests, i.e https://docs.lucee.org/recipes/mathematical-precision.html#dynamically-during-a-request Only the application scope is shared when using the same name in different application.cfc's

Thank you. It appeared rabbit hole is deeper. After some investigation, Application's this.name appeared to be correctly different between apps. Problem shows up when CFC are cached, there's seemingly random behavior, which CFC gets cached. Once reboot - all is ok. Second reboot - and wrong cfc is picked up. There's e.g. /model/gateway.cfc in both apps, but the contents is different, and 'wrong' cfc is being cached and used. I try to call method that I know exists, but Lucee says it's not, because cfc is picked from another project. I yet only see it from dev perspective, once I get access to Linux server, I will investigate deeper.

@micha fyi