Skip to content

Commit 3bfc645

Browse files
Minor fix
1 parent d7cd971 commit 3bfc645

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/automation/automation-child-runbooks.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,10 +46,9 @@ Currently, PowerShell 5.1 is supported and only certain runbook types can call e
4646
* The PowerShell types and the PowerShell Workflow types can't call each other inline. They must use `Start-AzAutomationRunbook`.
4747

4848
> [!IMPORTANT]
49-
> * Executing child scripts using `.\child-runbook.ps1` is not supported in PowerShell 7.1 and PowerShell 7.2
49+
> * Executing child scripts using `.\child-runbook.ps1` is not supported in PowerShell 7.1 and PowerShell 7.2
5050
**Workaround**: Use `Start-AutomationRunbook` ([internal cmdlet](/azure/automation/shared-resources/modules#internal-cmdlets)) or `Start-AzAutomationRunbook` (from [Az.Automation module](/powershell/module/Az.Automation/Start-AzAutomationRunbook)) to start another runbook from parent runbook.
51-
52-
> * Executing child scripts using Graphical PowerShell Workflow runbooks is not supported.
51+
> * Executing child scripts using Graphical PowerShell Workflow runbooks is not supported.
5352
**Workaround**: Use Start-AzAutomationRunbook (from [Az.Automation module](/powershell/module/Az.Automation/Start-AzAutomationRunbook)) from within the parent runbook (via an InlineScript block) to start another runbook.
5453

5554
The publish order of runbooks matters only for PowerShell Workflow runbooks.

0 commit comments

Comments
 (0)