After enabling script-specific Debugging by right-clicking on a custom script module and choosing Properties | Debugging, checking the box to enable, and setting the dropdown box to Trace script lines, variable assignments, and function calls the following error message is encountered during the runtime of the script:
The term 'saddc94e9-111c-4903-887c-b279cd64e295' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
There is no workaround for this issue. The script will execute as expected if Debugging is disabled by right-clicking on the script module and de-selecting the checkbox under Properties | Debugging.
Issue resolved in hotfix.