Arrrggg. We keep getting hit by intermittent template not found errors, and Element EXECUTIONMODE is undefined in THISTAG. Once it starts, there are a lot of them, missing the same file, which is the same one throwing the EXECUTIONMODE error. Clearing the template cache fixes it, but I'm not happy doing manual interventions to get the site back running. Happened yesterday, and again this morning. I've talked about this before, but since I don't have steps to repro not much came of it. We're not saving class files. Two completely different apps, different servers, different domains, one CF2018, one CF2021. Both ran for many years on CF9 without any of this. One of my colleagues has heard rumors that absolute paths for cfinclude and cfmodule are less reliable than relative paths. I'm reluctant to go through these big apps and change that everywhere, just to see if it makes a difference. Does anyone have any concrete experience that it did or didn't help in your case? Any other ideas?

Absolute paths, follow FILE SYSTEM and OS rules for access. IE d:\MyColdFusionCode\Something.CF would need permission to access d: read d: then at least read MyColdfusionCode\and then execute Something.CF whereas relative paths follow Network and then File System Rules.. KE D:\Coldfusion2021\wwwroot\SymlinktoMyColdfusionCode\Something.CF would use network user and group to access the file local user and or group. The OS differences from a Linux to Windows node from a high-level model are no different. An example would be cfinclude template = Something.CF" if run in the same directory would use the network service whereas cfinclude /hard/path/to/file/ works, but follows the OS file access rule. As for your template, or your server, check IO use and your page file settings. If its a Windows Server, you should exclude the entire directory running ColdFusion code from the antivirus engine.