Dagster max_concurrent sensor

The documentation does not provide a direct reference to a parameter specifically named

max_concurrent

for sensors. However, it does discuss various settings related to the concurrency and execution of sensors. For instance, the documentation mentions the use of threads for concurrency when launching dequeued runs, which can be controlled by the

dequeue_use_threads

and

dequeue_num_workers

settings in the

QueuedRunCoordinator

. These settings are not directly related to sensors but to how runs are dequeued and executed. When it comes to sensors, the documentation discusses the

use_threads

and

num_workers

settings within the sensor daemon configuration. These settings allow you to control the number of worker threads used by the sensor daemon when

use_threads

is set to

true

. This can indirectly affect the concurrency of sensor evaluations if multiple sensors are configured to run in parallel. Additionally, the documentation mentions that sensors have a default timeout of 60 seconds for their evaluation function, which can be adjusted using the

DAGSTER_SENSOR_GRPC_TIMEOUT_SECONDS

environment variable in Dagster Open Source or the

default_sensor_timeout

setting in Dagster Cloud. If you are looking to control the maximum number of concurrent sensor evaluations, you would typically look into the sensor daemon configuration and adjust the

use_threads

and

num_workers

settings accordingly. However, for a more specific parameter or setting named

max_concurrent

directly related to sensors, the documentation does not provide details. If you need further assistance with a specific use case or configuration, please provide more context or clarify your requirements.