# Q: Ticker stops when its actions' conditions are unmet. But should it?

**URL:** https://cl.desmos.com/t/q-ticker-stops-when-its-actions-conditions-are-unmet-but-should-it/4032
**Category:** Questions
**Created:** [February 7, 2022, 5:24pm UTC](https://cl.desmos.com/t/q-ticker-stops-when-its-actions-conditions-are-unmet-but-should-it/4032 "2022-02-07T17:24:56Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![pirsquared](https://avatars.discourse-cdn.com/v4/letter/p/4af34b/32.png) [@pirsquared](https://cl.desmos.com/u/pirsquared)
#### Post date: [February 7, 2022, 9:27pm UTC](https://cl.desmos.com/t/q-ticker-stops-when-its-actions-conditions-are-unmet-but-should-it/4032/4 "2022-02-07T21:27:49Z")

</div>

> [@Raj](#):
>
> The problem is that Desmos throws an error if I try to have more than _one_ action affecting t\_trial, because it views it as thereby getting defined in two different places.

You can get around this restriction by making sure the two actions have mutually-exclusive conditions, I believe - for example `t->t+1 {t<10}, t->0 {t=10}` or similar.

The solution is broadly the same as the problem we helped you with back in November. [Trouble getting correct count to show up at the right time - #6 by RajRaizada](https://cl.desmos.com/t/trouble-getting-correct-count-to-show-up-at-the-right-time/3854/6)

---

_[View the full topic](https://cl.desmos.com/t/q-ticker-stops-when-its-actions-conditions-are-unmet-but-should-it/4032)._
