Running 5.4.5.23 and I have an issue with multiple application.cfcs. I have been using the standard Sean Corfield application proxy approach for a year or 2 with no issue (Sean's post is gone now, but Cameron summarized it in his answer here https://stackoverflow.com/questions/12677326/application-cfc-extending-values-into-a-child-folder ). No issue running it with one sub dir having its own application.cfc extending ApplicationProxy. All application.cfcs have the same this.name property set - so they can share the root app's app scope vars. Each child onApplicationStart() calls super.onApplicationStart() - which has a condition to check to see if has already loaded up before it reloads all its app scope vars. What I was expecting was that each sub dir's app.cfc would still get its onApplicationStart() event called when the first request was made to that subdir - so it could init a few of its own variables as needed - like say the Taffy application variable. Not the case. They are all one app - so they only get one start. Unless I am missing something, then I guess I need to either put all the app var initialization in the root app.cfc, or extract any init logic in the subDir onApplicationStart()s into separate functions and have the child onRequestStart() call that if it has not run. Any better ideas?

You don't explicitly mention if this behaviour is new or if it occurs with a previous versions, too?

deleted the last reply - sorry - I had posted on ghost scheduler issues and thought your comments related to that. Multi-tasking taking a toll on me. At least a couple of months and definitely on 5.4.4.38 this has been happening, but TBH I assumed it was expected behavior and i just misunderstood the lifecycle.