# Disabled Execute Condition on Stop Run Action

**URL:** https://www.finalbuilder.com/forums/t/disabled-execute-condition-on-stop-run-action/144
**Category:** Discussion
**Created:** [July 27, 2006, 3:18am UTC](https://www.finalbuilder.com/forums/t/disabled-execute-condition-on-stop-run-action/144 "2006-07-27T03:18:34Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![ken\_turner](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/k/7993a0/32.png) [@ken\_turner](https://www.finalbuilder.com/forums/u/ken_turner)
#### Post date: [July 27, 2006, 3:18am UTC](https://www.finalbuilder.com/forums/t/disabled-execute-condition-on-stop-run-action/144/1 "2006-07-27T03:18:34Z")

</div>

In FB 4.1.0.228, the Execute Condition on the Properties tab of the Stop Run Action is disabled. Is this by design, and if so, any special reason why?

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [July 28, 2006, 3:03am UTC](https://www.finalbuilder.com/forums/t/disabled-execute-condition-on-stop-run-action/144/2 "2006-07-28T03:03:03Z")

</div>

This is by design, the Stop Run action is a special case that doesn’t go through the normal code path in the execution engine, so it never gets to the part where the condition is evaluated.   
  
To work around this, add an action group with a condition and make the Stop action a child of the action group.

---

<div class="post-metadata">

### Author: ![ken\_turner](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/k/7993a0/32.png) [@ken\_turner](https://www.finalbuilder.com/forums/u/ken_turner)
#### Post date: [July 28, 2006, 8:51am UTC](https://www.finalbuilder.com/forums/t/disabled-execute-condition-on-stop-run-action/144/3 "2006-07-28T08:51:14Z")

</div>

Thanks, Vincent, I’d already done exactly that as a workaround.  
  
Cheers  
  
Ken