# Under Which Conditions Exactly to App Start Triggers Fire?

**URL:** <https://community.tulip.co/t/under-which-conditions-exactly-to-app-start-triggers-fire/16009>\
**Category:** Support, Troubleshooting, & Help\
**Tags:** triggers, ai-trigger, app-start\
**Created:** [January 15, 2026, 7:11pm UTC](https://community.tulip.co/t/under-which-conditions-exactly-to-app-start-triggers-fire/16009 "2026-01-15T19:11:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmlowden](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/jmlowden/32/8645_2.png) [@jmlowden](https://community.tulip.co/u/jmlowden)\
**Post date:** [January 15, 2026, 7:11pm UTC](https://community.tulip.co/t/under-which-conditions-exactly-to-app-start-triggers-fire/16009/1 "2026-01-15T19:11:12Z")

</div>

I know this sounds like an easy answer, but I’m curious about expected behavior for all the transitions options completing the app and navigating to the same app or another app, to the splash screen, to the first step or a specific step, etc.

As I’m reviewing completions data it looks like I’m only firing the app start triggers when I restart the app or change the app from the Menu button, but not when I complete the app and go to a specific step within the same app:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/5/581453c500fd51d41f60983223bf34d528855707.png)

---

<div class="post-metadata">

**Author:** ![OlgaStroilova](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/olgastroilova/32/7199_2.png) [@OlgaStroilova](https://community.tulip.co/u/OlgaStroilova)\
**Post date:** [January 16, 2026, 9:43pm UTC](https://community.tulip.co/t/under-which-conditions-exactly-to-app-start-triggers-fire/16009/3 "2026-01-16T21:43:36Z")

</div>

Hi @jmlowden , that’s odd - for newer LTS versions, App start triggers should fire on every restart including Complete & goto step… Which LTS version/instance are you on right now?

If more comfortable sharing this information privately, please feel free to open a Tulip support ticket.

---

<div class="post-metadata">

**Author:** ![HCEH](https://avatars.discourse-cdn.com/v4/letter/h/5fc32e/32.png) [@HCEH](https://community.tulip.co/u/HCEH)\
**Post date:** [January 19, 2026, 7:57am UTC](https://community.tulip.co/t/under-which-conditions-exactly-to-app-start-triggers-fire/16009/4 "2026-01-19T07:57:47Z")

</div>

Hi @OlgaStroilova

This may be highly relevant for other customers, so please share the details in this thread.

We are heavily dependant on that this feature works as expected.

Thanks!

---

<div class="post-metadata">

**Author:** ![thorsten.langner](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@thorsten.langner](https://community.tulip.co/u/thorsten.langner)\
**Post date:** [January 19, 2026, 9:05am UTC](https://community.tulip.co/t/under-which-conditions-exactly-to-app-start-triggers-fire/16009/5 "2026-01-19T09:05:31Z")

</div>

I tested it and it works as I expected.  
If the App is open and you close and reopen the player, it is not an app opening. So it will not fire.  
But whenever you restart the app or switch to it or enter it by splash screen, it should fire.

I tested it with your exact same trigger and a “show message” on app start. And as expected, the message appears every time…

Simplified: Whenever the app execution time starts at 00:00:00

---

<div class="post-metadata">

**Author:** ![jmlowden](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/jmlowden/32/8645_2.png) [@jmlowden](https://community.tulip.co/u/jmlowden)\
**Post date:** [January 20, 2026, 4:09pm UTC](https://community.tulip.co/t/under-which-conditions-exactly-to-app-start-triggers-fire/16009/6 "2026-01-20T16:09:30Z")

</div>

We are LTS 14.4, but private cloud (hopefully not for too much longer).

We do have a support ticket open for our specific issue, thank you for confirming the expected behavior.
