I am in the process of developing an azure function app (powershell). The function app is made up of a number of functions that are triggered by various queues (and moves the state between the queues).

I am seeing occasions where when viewing the output of an invocation, I see the following error:

The term ‘write-output:’ is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. Exception : Type : System.Management.Automation.CommandNotFoundException

All of the child functions are using the same write-output command to write logging information to the host for troubleshooting reasons. This is causing some of my try catches to fail, as it is seeing the error when trying to output to the host.

I would have expected this to refresh the powershell session and restore anything that was missing