Understanding scope of functions in powershell workflow

Question

Copy and paste the following into a new Powershell ISE script and hit F5:
workflow workflow1{
"in workflow1"
func1
function func1 {
"in func1"
func2
function func2 {
"in func2"
workflow1
the error I get is:
The term 'func2' is not recognized as the name of a cmdlet, function, script file, or operable program
I don't understand this. Why would func1 be in scope but not func2? Any help much appreciated. TIA.

Answer 1

Hi guys,
I had a similar conversation over on SO: Understanding
scope of functions in powershell workflow
I'll say here what I said there:
To vaguely summarise all the responses, don't question why it behaves this way, just accept that it does and deal with it. Fair enough.
I've written a whole deployment pipeline in none-workflow Powershell and I'd like to optimise it by using workflow's "foreach -parallel" however it seems the tax on doing so is that I'd have to go back and re-write the whole thing in workflow. That's
too big a tax to pay unfortunately just to get a parallel foreach loop.
Lesson learned - use Powershell workflow from the get-go.
Corallary #1 - Understand the technology before using it.  It saves you from future pain.
¯\_(ツ)_/¯