Discovery | Pattern Debugger indefinitely stuck on first step of all patterns with "Debug in progress" until cancelledIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Pattern Debugger is getting stuck on the first step of any pattern with the message "Debug in progress" and requires the Debug to be cancelled in order to exit. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } • All Patterns are impacted and Pattern Debugger can't be used. • The Debug Progress window will show the MID Server the pattern is running on, Starting step: 1 and Finished step: 1 indicating that MID Server processed the step and returned the payload to the ECC Queue but the instance is not processing the input record. • The ECC Queue will have an input record for the processed step where Agent is the MID Server, Topic is PatternDebuggerProbe, State is error, and Error String is No sensors defined. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Releases Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The Pattern Debugger probe requires the Pattern Debugger Sensor to process the probe's input. If the sensor is not defined for any of the below reasons, the instance will not process the probes input and Pattern Debugger will remain stuck with message 'Debug in progress', requiring the Debug to be manually cancelled. • The Pattern Debugger Sensor is set to Active = false' • The Reacts to probe field on the Pattern Debugger Sensor is not referencing the Pattern Debugger probe. • The Pattern Debugger Sensor is missing on the instance. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. Go to Discovery Definition > Sensors. 2. Add the Reacts to probe and Active fields to the list view. 3. Filter the list where Name is Pattern Debugger Sensor. a. If The Pattern Debugger Sensor is set to Active = false. Set it to Active = true. b. If the Reacts to probe field on the Pattern Debugger Sensor is not referencing the Pattern Debugger probe. • Set it to reference the Pattern Debugger probe. c. If the Pattern Debugger Sensor is missing on the instance. • Go to the Deleted Application File [sys_metadata_delete] table. • Filter the list where Display Name is Pattern Debugger Sensor and Table name is Sensor. -- If a Deleted Application File record is found. • Open the record and click the Restore File button. -- If a Deleted Application File record is NOT found. The Pattern Designer plugin needs to be repaired to reinstall the sensor. • Go to the Plugins module to open Application Manager • Search for com.snc.pattern.designer • Go to the Installed tab • Find Pattern Designer under Family plugins and open it • Under the Quick Actions section, find and click Repair 4. Go to Discovery Definition > Probes 5. Find and Open the Pattern Debugger probe. 6. Verify that the Pattern Debugger Sensor is listed in the Sensors That React to This Probe related list and is Active = true. 7. Load a pattern in Pattern Debugger and verify that Debug is now progressing past step 1.