Hey all, I think my team found a bug with how Dagster handle's run history for dependency sensors. We have two jobs in two separate workspaces but that have the same name, but when I look at the run history for the job in the sensor it's including both separate jobs in it's run history. Note the differing run times/time to finish of both jobs

Hi! Thanks for bringing this to our attention. Has this been happening or is this recent? And what are you referring to when talking about a dependency sensor?

This is more recent since we haven't had any job with duplicate names in different workspaces until recently. And sorry for not explaining further but we track assets in sensors in order to know when to kick off jobs. Our team calls these "dependency sensors" since the sensor is listening for "dependencies" in order to know when to kick off a job. At the end of the day it's just a regular sensor with extra logic.