# ask-community

Célio de Assis Picanço Filho

03/28/2022, 2:47 PM
Hi, everyone I'm trying to understand and apply schedules in dagster. For this, I tried creating a new project with the
dagster new-project
. This worked fine, however, when I try running the dagster-daemon from the directory where the workspace.yaml file is located, I get the message:
Copy code
Schedule my_hourly_schedule was started from a location Scheduler that can no longer be found in the workspace, or has metadata that has changed since the schedule was started. You can turn off this schedule in the Dagit UI from the Status tab.
Schedule is the name of my project. Does anyone knows what could be the problem here? Thanks in advance.


03/28/2022, 2:57 PM
Hi Célio, if you go to the ‘workspace’ tab in Dagit, you should see a list of repository locations. That error implies that there was a location titled “Scheduler”, but it has been removed
Maybe it has been renamed “Schedule” per your message?

Célio de Assis Picanço Filho

03/29/2022, 7:20 AM
Hi, Johann. Unfortunately, that is not the case. I've posted the same question on stack overflow with an image that shows my directories: So there directory is there as well as the yaml file. Please notice that my DAGSTER_HOME variable is also pointing at the directory where the yaml file is located.
I'm trying this in a simplified set up now I put everything on the same folder. When I run the dagster-daemon now, I don't get the message from above anymore. However, the runs still don't execute. To my surprise, when I check the daemon_heartbeats table in the runs.db that dagster generates automatically, a hearbeat is sent there every minute Any Ideas ?


03/29/2022, 11:56 AM
Hi Célio - is it possible to post logs from your dagster-daemon process covering a time when you were expecting a run to launch? Did you start the schedule in Dagit?

Célio de Assis Picanço Filho

04/04/2022, 10:49 AM
Hi, Daniel Thanks for your reply. Over the last few days I've been trying to figure out how to schedule jobs in dagster, as it would be crucial to use this in production. However, even in the simplest scenario (which I'm sharing with you in this message), I get the same message. Here is the python Code I'm trying to schedule as well as the logs for a given timeframe. I've also included the dagit interface showing that the schedule is active and the daemons are healthy. I would appreciate if you could help. Thanks


04/04/2022, 4:13 PM
Hi Célio. Usually, when we see something like this, it’s because
is run in a different environment (maybe a different Python executable?) than
. To prevent these type of sync issues, can you make sure the two commands are run in exactly the same way?
We’re also rolling out a fix this week to hopefully address this whole class of issues