Interestingly if you have two jobs with the same name in two different code locations Dagster seems to have trouble differentiating between their runs - a run in a job from one code location will show up in the runs history for a job with the same name in a different code location. The status page is a good place to see this - concordance_dnax was launched when there was one user code location, then I deployed user code location from a different branch (with all the same jobs) and now it shows two concordance_dnax jobs that point to the same run.

We should be able to differentiate these now with https://github.com/dagster-io/dagster/pull/6893… can check in with the team