IssueTracker

Chester: do we have a list of the error codes where this link does not make sense to show?

Depends on what kind of error codes we're talking about. For failure cases in the whole pipeline, we do have a per-failure case handling and possible resolution actions. But in this case, it's a specific installation failure, which we don't have individual handling for (note that this is also one failure case we don't explicitly explain, so it falls into the general install fail category). But this isn't really the problem here.

The problem is that the action ID associated with the run isn't getting set (i.e. normally the user clicks the Run/Debug/AC/ACC buttons and we keep around that action ID, which is exactly what's needed for "retry"), so I'm not sure how the user got to a point where the ID is basically mapping to a deployment action that isn't working.

@phileo99 What button did you press to start the installation? Run? Debug?

Repro'd also on Mac:
Android Studio 3.5.1
Build #AI-191.8026.42.35.5900203, built on September 25, 2019
JRE: 1.8.0_202-release-1483-b49-5587405 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.6

Steps to repro:
Initial build variant:
productFlavor = dev
buildType = debug

in IDE press play (ie. Run app) to load devDebug build variant into physical device without issues

Then switch to a different build variant:
productFlavor = staging
buildType = release

do gradle sync, clean
then press play and observe error with broken Retry link