# Workflow that only responds to signals

**URL:** <https://community.temporal.io/t/workflow-that-only-responds-to-signals/2930>\
**Category:** Community Support\
**Tags:** go-sdk\
**Created:** [September 14, 2021, 10:36pm UTC](https://community.temporal.io/t/workflow-that-only-responds-to-signals/2930 "2021-09-14T22:36:10Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [September 15, 2021, 2:02am UTC](https://community.temporal.io/t/workflow-that-only-responds-to-signals/2930/3 "2021-09-15T02:02:28Z")

</div>

If you are waiting for a single signal type you don’t need the selector. Just call `nameChan.Receive` in a loop. As @mleow pointed out if you need to process a very large number of signals then it is recommended to call ContinueAsNew periodically (let’s say every 1k signals received) to keep the workflow event history size bounded.

---

_[View the full topic](https://community.temporal.io/t/workflow-that-only-responds-to-signals/2930)._