# Best practices around Guardian timeout

**URL:** <https://community.auth0.com/t/best-practices-around-guardian-timeout/6398>\
**Category:** Get Help\
**Tags:** guardian, mfa\
**Created:** [April 28, 2017, 4:56am UTC](https://community.auth0.com/t/best-practices-around-guardian-timeout/6398 "2017-04-28T04:56:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike99](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@Mike99](https://community.auth0.com/u/Mike99)\
**Post date:** [April 28, 2017, 4:56am UTC](https://community.auth0.com/t/best-practices-around-guardian-timeout/6398/1 "2017-04-28T04:56:43Z")

</div>

I am using guardianjs in order to customize my guardian page. I noticed that the timeout seems to be connected to the transaction. Is it ok to simply start another transaction when using guardianjs.start() when I’ve detected that the user has timed out?

If so, that would be trivial if the user hasn’t entered a phone number, but if they had, how would that work?

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:53am UTC](https://community.auth0.com/t/best-practices-around-guardian-timeout/6398/2 "2018-03-02T05:53:33Z")

</div>


