I've copy-pasted some code and it's Friday so I overlooked that I didn't copy CFQUERY tag, only inner SQL with cfqueryparams. I should have wear glasses 🙂 But, Lucee didn't get any error when encountered cfqueryparam outside cfquery tag. The page didn't throw any error, but also did nothing, since there output was silenced. I think things like cfqueryparam cfhttpparam should check for a proper parent tag.

Not sure anyone noticed but I have seen my lucee application was running great on version 5 and it’s seems slowed down on 6 My application consists of lots of uploads and working with internal arrays and structs

Yeah pretty sure CF does this. Code def should not just do nothing. It should either do what it suggests it should do, or if it can't: it should error. Did you raise a Jira ticket for this?

investigated a bit more, Lucee 6 has no issue, throwing error, however if inside function, it will not throw error until function is called, but it's not bug I guess