When developing an application, inserting breakpoints and/or the command TRACE in code can be useful for pausing code execution at certain points to debug issues. During deployment, if an application happens to be started in headless mode, the breakpoints and any TRACE are ignored, even if the application is not compiled or merged (i.e. still in interpreted mode). Thus, there is no need to be concerned if an interpeted application being run headless had any TRACE or breakpoints remaining in its code; the execution will not stop solely because of those. Conversely, do not expect execution to pause in this scenario, just because there was a TRACE or breakpoint left in the code.