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

dagster

Hello,
I'm attempting to use <https://docs.dagster.io/_modules/dagster_msteams/sensors#make_teams_on_run_failure_sensor|msteam failure sensor> but am facing an issue with generated card/Teams message: the link from `View in Dagit` button is in the format `{dagit_base_url}/instance/runs/{run_id}`
which redirects to `{dagit_base_url}/overview/timeline` due to the `/instance` component. The correct link is `{dagit_base_url}/runs/{run_id}` .
Is it a known bug or a potential misconfiguration on my end of the sensor ?

Also, why does `make_teams_on_run_failure_sensor` monitored_jobs parameter does not cover `CodeLocationSelector` like slack sensor does ?

The default configuration seems to catch errors from other code location instead of the current.

```ob __ASSET_JOB_0 failed!
Run ID: XXXXXXXX
Error: This run has been marked as failed from outside the execution context```
We are wondering if it's due to monitored_jobs not being set.

i believe the url is an oversight. mind filing an issue so we can get to it?

Hello yuhan,
I've just opened an issue : <https://github.com/dagster-io/dagster/issues/14136>
Let me know if something missing.

Do you have any suggestion about my second issue (failure sensor catching failure from other code location) ?