# What Guarantees Exist (If Any) for Draining Signals?

**URL:** <https://community.temporal.io/t/what-guarantees-exist-if-any-for-draining-signals/10338>\
**Category:** Community Support\
**Tags:** go-sdk\
**Created:** [December 10, 2023, 5:35pm UTC](https://community.temporal.io/t/what-guarantees-exist-if-any-for-draining-signals/10338 "2023-12-10T17:35:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AlbertL](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/albertl/32/2825_2.png) [@AlbertL](https://community.temporal.io/u/AlbertL)\
**Post date:** [December 10, 2023, 5:35pm UTC](https://community.temporal.io/t/what-guarantees-exist-if-any-for-draining-signals/10338/1 "2023-12-10T17:35:52Z")

</div>

Hi,

Let’s say I have the following simple workflow.

```auto
func SimpleSignalWorkfow(ctx workflow.Context) error {
	err := workflow.Sleep(ctx, 24*time.Hour)
	ch := workflow.GetSignalChannel(ctx, "signal")
	var s string
	for ch.ReceiveAsync(&s) {
		workflow.GetLogger(ctx).Info(s)
	}
	return err
}

```

What guarantees exist, if any, that a signal won’t be missed? Couldn’t the Temporal server receive a signal for that workflow run after the worker existed the for-loop? Wouldn’t that result in a signal being dropped?

If so, how should I write this workflow to prevent signal loss?

Thanks!

Albert

---

<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:** [December 10, 2023, 7:05pm UTC](https://community.temporal.io/t/what-guarantees-exist-if-any-for-draining-signals/10338/2 "2023-12-10T19:05:17Z")

</div>

Temporal detects the race condition you described, rolls back the workflow state to the Sleep line, and then executes the workflow with the new signal.