Several Dagster features, like schedules, sensors, and run queueing, require a long-running dagster-daemon process to be included with your deployment.
The easiest way to run the Dagster daemon locally is to run the dagster dev command:
dagster dev
This command launches both Dagit and the Dagster daemon, allowing you to start a full local deployment of Dagster from the command line. Refer to the Running Dagster locally guide for more information about dagster dev.
To run the Dagster daemon by itself:
dagster-daemon run
This command takes the same arguments as dagster dev for specifying where to find your code.
The dagster-daemon process reads from your Dagster instance file to determine which daemons should be included. Each of the included daemons then runs on a regular interval in its own threads.
If the daemon is configured to use a workspace file to load code location(s), note that they will periodically reload the file. This means that the dagster-daemon process doesn't need to be restarted when workspace files are changed.
To check the status of the dagster-daemon process within Dagit:
In the top navigation, click Deployment.
Click the Daemons tab.
This tab displays information about all the daemons currently configured on your instance.
Each daemon periodically writes a heartbeat to your instance storage. If a daemon doesn't show a recent heartbeat, check the logs from your dagster-daemon process for errors.