The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Hi team, running into another weird problem. We added a new job and sensor but the sensor was never ticked. I am seeing this in the logs:

```WARNING[0m - Sensor new_job_sensor was started from a location fabricator that can no longer be found in the workspace. You can turn off this sensor in the Dagit UI from the Status tab.',
}```
new_job_sensor is the name of our sensor and fabricator is our repo name. The other old sensors seem to work ok.

did you add the new sensor into the `Definitions`  or `@repository`? looks like `new_job_sensor` was once loaded fine but then no longer loaded in the `fabricator` repo.

this happens to me sometimes, when i changed the sensor name. then i needed to turn off the old name and turn on the new one from the Sensors page.

Hmmm..we add sensor to the Definitions with CachingRepositoryData.from_list()