# Extensible timer design

**URL:** <https://community.temporal.io/t/extensible-timer-design/4853>\
**Category:** Community Support\
**Tags:** general-impl\
**Created:** [June 1, 2022, 11:32pm UTC](https://community.temporal.io/t/extensible-timer-design/4853 "2022-06-01T23:32:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ggissel](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/ggissel/32/2134_2.png) [@Ggissel](https://community.temporal.io/u/Ggissel)\
**Post date:** [June 1, 2022, 11:32pm UTC](https://community.temporal.io/t/extensible-timer-design/4853/1 "2022-06-01T23:32:22Z")

</div>

I would like to make a workflow that listens to signals. As long as signals are coming in, I’d like it to run (up to a point; after some longer time period I’d like to stop listening and do something with the received signals).

I thought I could do this by setting a timer and then canceling/creating a new timer when a signal comes in. It seems like the first timer future always resolves even when I cancel it.

I think I’m missing something really basic here

---

<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:** [June 2, 2022, 5:34pm UTC](https://community.temporal.io/t/extensible-timer-design/4853/2 "2022-06-02T17:34:11Z")

</div>

What is the SDK you are using? It can be SDK specific. In general when a timer is canceled its future is resolved immediately with a cancellation failure/exception.
