From d0c972dcfbcfb7fb6fc022a109a28bf3fcaeaf85 Mon Sep 17 00:00:00 2001 From: Michael Chisholm Date: Tue, 7 Sep 2021 18:21:29 +1000 Subject: [PATCH] Clarify that `condition` only stops current sequence (#19238) --- source/_docs/scripts.markdown | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown index f76598b68eb..925ab15e1c0 100644 --- a/source/_docs/scripts.markdown +++ b/source/_docs/scripts.markdown @@ -92,7 +92,13 @@ The variables action allows you to set/override variables that will be accessibl ## Test a Condition -While executing a script you can add a condition to stop further execution. When a condition does not return `true`, the script will stop executing. There are many different conditions which are documented at the [conditions page]. +While executing a script you can add a condition in the main sequence to stop further execution. When a condition does not return `true`, the script will stop executing. There are many different conditions which are documented at the [conditions page]. + +
+ +The `condition` action only stops executing the current sequence block. When it is used inside a [repeat](#repeat-a-group-of-actions) action, only the current iteration of the `repeat` loop will stop. When it is used inside a [choose](#test-a-condition) action, only the actions within that `choose` will stop. + +
```yaml # If paulus is home, continue to execute the script below these lines