# Limit workflow-based concurrent executions?

**URL:** <https://community.temporal.io/t/limit-workflow-based-concurrent-executions/633>\
**Category:** Community Support\
**Tags:** go-sdk\
**Created:** [September 16, 2020, 6:14am UTC](https://community.temporal.io/t/limit-workflow-based-concurrent-executions/633 "2020-09-16T06:14:05Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![hundt](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@hundt](https://community.temporal.io/u/hundt)\
**Post date:** [November 17, 2020, 2:23pm UTC](https://community.temporal.io/t/limit-workflow-based-concurrent-executions/633/6 "2020-11-17T14:23:10Z")

</div>

For anyone who might find this thread on Google and be wondering about my question: see [this later thread](https://community.temporal.io/t/continueasnew-signals/1008/2) in which I provided some pared-down example code. The bottom line is that you should drain all open signal channels immediately before returning if you wish to ensure that you did not miss any signals.

---

_[View the full topic](https://community.temporal.io/t/limit-workflow-based-concurrent-executions/633)._