App import transition missed with apps already deployed in target environment

When an already deployed application is upgraded using the import feature, and the trigger “Complete App Then Change to Step” is used to navigate to the upgraded deployed app, the reference to the step is deleted despite the target still being there.

We would like to request a solution for that gap, as it affects scalability.

Importing by app groups isn´t feasible as other apps wouldn´t need to have an update.

I am not sanctioning this as a great solution, but it is a solution…

You can switch these triggers to Go to App and Step by a static value name.

However, this means that the name of your apps will become a critical unique identifier.

Hi Ricardo, Dan’s suggestion is the best current way to solve this. I agree that this is a subpar experience.

The reason this happens is that in the “Complete App and Change to Step” trigger, we are unable to tell that the app in the transition is the same one that you are currently in. We will look to see if there is an easy way to fix this.