It’d be nice if dagster run monitoring’s setting

start_timeout_seconds

respected the value of

DAGSTER_GRPC_TIMEOUT_SECONDS

of the current running grpc code server 😉

Hi! Thanks for bringing this up. This is really tactical feedback. Do you mind opening up a GitHub Issue so we can triage and not lose track of this? https://github.com/dagster-io/dagster/issues/new/choose

Yes I can do that!