Schedules don't run

Summary

I have a Dagit with 4 repositories, each with different schedules.
Ussually the run perfectly but now the aren’t runing and there is no advice, no error, no nothing.
I’m traing localy by changin the time and waiting but nothing, traing to removing all the Dagit folders that create with history and logs, but nothing to.
I try to find something in the issues here, or in stack overflow but nothing to, that’s why I’m creating this issue.

Reproduction

1. Create solids
2. Create pipelines
3. Create schedule
4. Create repository
5. Run dagit

Dagit UI/UX Issue Screenshots

Additional Info about Your Environment

requirements.txt I need to specify the flask and Werkzeug version because with the new flask and new Werkzeug I have a socket error.

flask==1.1.4
Werkzeug==1.0.1
dagster==0.10.5
dagit==0.10.5
dagster-cron==0.10.5
dagster-pandas==0.10.5

dagster.yml

scheduler:
  module: dagster_cron.cron_scheduler
  class: SystemCronScheduler

telemetry:
      enabled: false

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We factor engagement into prioritization.

[gibsondan]

No problem! this stuff is complicated/hard to debug when issues come up, esp when the logs don’t appear in Dagit. Glad it’s working!

[gibsondan]

A couple of options:

• If you use the DefaultRunLauncher rather than the DockerRunLauncher (by taking out the ‘run_launcher’ key from your instance yaml), it will launch the run within that same container instead of in a new container. That way it should have access to all the environment variables (but you don’t get one container per run which is nice for some things)

• If you do want to use DockerRunLauncher, you need to configure it with all the environment variables as part of the run launcher config (it would be nice if there was some way to tell it to make a ‘copy’ of an existing service/container rather than just create a new container using the same image, but we don’t have anything like that currently). Unfortunately I don’t think the docker API for python has support for env files yet, so you may need to list out the environment variables individually for now (like you are currently listing DAGSTER_POSTGRES_USER etc.).