Script error while attempting to launch Shazzam undefinedThe error "Script error while attempting to launch Shazzam undefined" may get logged when triggering a Discovery schedule. This error is produced by the ShazzamLaunch.launch() script include function call. You can debug this via the Script Debugger, or by adding log statements to the script include. To trigger the breakpoint in the script debugger, the discovery would need to be triggered via scripts - background: // discovery schedule sys_idvar schedID = ""; // discovery schedule sys_trigger record sys_idvar schedTrigger = ""; var schedGR = new GlideRecord('discovery_schedule'); schedGR.get('sys_id', schedID); var schedTriggerGR = new GlideRecord('sys_trigger'); schedTriggerGR.get('sys_id', schedTrigger); var sd = new StartDiscovery(); sd.startFromSchedule(schedGR, schedTriggerGR); The above code is from the "Debug ecc queue output creation" section of Discovery Phase Shazzam article. Possible Causes Cause 01: Discovery functionalities in discovery behaviors have invalid/non-existing mid servers specified on the mid servers field. Solution: Make sure only valid mid servers are assigned to the mid server field in the discovery functionalities. Cause 02: The schedule is a "Network" schedule. Because this is a 'Network' Discovery, Discovery will query the 'discovery_function_def' table for an entry named 'SNMP only' to get the right port probes to launch for Shazzam.If the out of the box entry's name was changed from 'SNMP only' to something else, Discovery is prevented from pulling up the right record and NULL value was returned.This caused exceptions further down the execution when Discovery attempts to launch Shazzam probe(s). Solution: Changing the name back to 'SNMP only' Cause 03: Invalid discovery ranges associated with the schedule. Such ranges could have been incorrectly imported or created via scripts. One example would be a range of type "IP Address Range" with no start/end IPs Solution: Correct any invalid ranges.