Please feel free to provide feedback or file bugs here.

Deep nested workflows don't recognize the erroraction parameter

Votes from Connect: 5

Original Date Submitted: 3/2/2015 8:58:03 PM

Description:
********Contact Information********
Handle: Trond Hindenes
Site Name: PowerShell
Feedback ID: 1156994
***************************************

Frequency: Always Happens
Regression: I do not know if this issue existed previously

Problem Description:
If a workflow uses deep nesting (at least 3 levels of nesting), erroraction does not work. This is reproducable in both the V4 and V5 feb preview of the WMF.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1156994 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1156994).

Repro Steps:
Consider the following 3 workflows
workflow one
{
Write-Output "one"
}

workflow two
{
one

}

workflow three
{
two -ErrorAction Stop
}

this code does not compile. If removing the "ErrorAction" parameter in workflow three, it works.

Expected Results:
workflow should compile.

Internal BugId: 14275

1 vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)

We’ll send you updates on this idea

AdminJoey Aiello [MSFT] (Program Manager, Windows Server) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base