# Change timeout in "email not open" automation

**URL:** https://forum.mautic.org/t/change-timeout-in-email-not-open-automation/24101
**Category:** Product Support
**Created:** [May 15, 2022, 11:39am UTC](https://forum.mautic.org/t/change-timeout-in-email-not-open-automation/24101 "2022-05-15T11:39:54Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![xmontero](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/xmontero/32/7499_2.png) [@xmontero](https://forum.mautic.org/u/xmontero)
#### Post date: [May 15, 2022, 11:39am UTC](https://forum.mautic.org/t/change-timeout-in-email-not-open-automation/24101/1 "2022-05-15T11:39:54Z")

</div>

How can I change the “timeout” by which an email is considered “not open”?

For testing and eucational purposes I want that when an email is sent, if open within, say, 1 or 2 minutes it’s considered “open”. But after 3 minutes “not open” it triggers the “not open” branch.

---

<div class="post-metadata">

### Author: ![joeyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/joeyk/32/11164_2.png) [@joeyk](https://forum.mautic.org/u/joeyk)
#### Post date: [May 15, 2022, 3:21pm UTC](https://forum.mautic.org/t/change-timeout-in-email-not-open-automation/24101/2 "2022-05-15T15:21:32Z")

</div>

You can set the no branch within 3 minutes. Make sure you send emails immediately and your mautic:campaign:update and trigger crons are processing every minute.

---

<div class="post-metadata">

### Author: ![xmontero](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/xmontero/32/7499_2.png) [@xmontero](https://forum.mautic.org/u/xmontero)
#### Post date: [May 18, 2022, 2:46pm UTC](https://forum.mautic.org/t/change-timeout-in-email-not-open-automation/24101/3 "2022-05-18T14:46:36Z")

</div>

Thanks joeyk. I already process the `:update` and `:trigger` minutely.

The question is “where do I tell mautic” that the “no read” signal should be “after X minuts/hours/days”? Currently in a test it took like 7 days to consider the emails “not read”.

---

<div class="post-metadata">

### Author: ![joeyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/joeyk/32/11164_2.png) [@joeyk](https://forum.mautic.org/u/joeyk)
#### Post date: [May 18, 2022, 4:26pm UTC](https://forum.mautic.org/t/change-timeout-in-email-not-open-automation/24101/4 "2022-05-18T16:26:30Z")

</div>

Sure.  
In the No branch you need to execute the next action after 2 minutes. That is equivalent to “how long to wait until it’s considered no”.  
I understand, that you have to wait 7 days for the next action also, so you have to place a dummy action in the no branch. Like adding and deducting points.

---

<div class="post-metadata">

### Author: ![xmontero](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/xmontero/32/7499_2.png) [@xmontero](https://forum.mautic.org/u/xmontero)
#### Post date: [May 19, 2022, 5:50pm UTC](https://forum.mautic.org/t/change-timeout-in-email-not-open-automation/24101/5 "2022-05-19T17:50:49Z")

</div>

Ah, will try and comment here! Thanks!

So I guess really there’s an “output” going immediately via the “no” and is “locked” by the “wait”. If for any reason the email is “open” the lead is “changed” from the “downstream-no” (even it left the decission box) up to the mail-read decission box again and down again over the other brnach? Does it really work like this?

I always thought that when a lead leaves any state down it does not roll-back up again.
