Created pattern from generic application or from AFP is not working as expectedWhen a new class is created from Generic Application or from AFP the process classifier is created in discovery_classy_proc table. The pattern is created with "Enforce Process Classification" checked on and without the process name in the identification section. During Top Down discovery Pre Pattern Execution flow checks the process name that is running on the Entry point - Host:port in cmdb_running_process table. In case the process was not found in cmdb_running_process on the port of EP will be thrown the following message in the Discovery log: Pre Pattern Execution2022-11-29 09:17:39: Getting pre pattern execution data generated by script.2022-11-29 09:17:39: script: ProcessInfoWindows - message: Process not found in cmdb In this case, classification will be failed, the pattern will be triggered, but won't run and the application will be recognized as Generic Application. The problem is that we are skipping the listening port id section in case that process wasn't classified but it has classifiers and "Enforce Process Classification" is true. Generic Application pattern always runs the listening port flow and the process was found using this flow. The solution for the issue can be moving classification to the pattern identification section: Then disable "Enforce Process Classification" and deactivate Process classification because process classification was moved to the pattern. Next time Top Down will be run the process will be found by listening port flow and recognized as newly created class.