Auto-logout & Timer Trigger / App Start Combo to Force App Refresh

Working through some iterative development testing with a user today and came across the issue that my trigger edits were not being reflected because they were still were still running a prior version (snapshot vs. current development version) of the app from a completion that had been started but not ended.

It occurred to me that I could probably force the app to refresh leveraging our automatic logout and timer and/or app start triggers to cancel the app if the timer expires when there is no logged in user.

Is anyone doing something like this? Best practices?

As I think about it I wonder if there would be a value to having App timer triggers vs. step timer triggers.

Or perhaps a better fix is to make this configurable at the app, station, or instance level - apps are cancelled when the user is logged out.

Curious what others think about this.

I have a custom widget, to check if the app is opened (not started).
This trigger works if the app is started, but also if you open the player with an already started app.
No matter on what step.

With this trigger you can check for the most recent version and execute a restart.

However, this only works, when the running app already has this feature :wink:

Great idea, to use the logout feature temporarily :slight_smile: