we’re trying to setup a basic schedule and they successfully show up in ui…however on the tick it doesn’t actually launch the run and we see the following in the logs:

#033[32m2023-05-23 19:47:00 +0000#033[0m - dagster.daemon.SchedulerDaemon - #033[34mWARNING#033[0m - Schedule my_schedule was started from a location dagster_jobs that can no longer be found in the workspace. You can turn off this schedule in the Dagit UI from the Status tab.

hi @Caleb Overman! how are you running your daemons / dagit? based on that message, it's possible that the daemon is looking at a different code location than the ui

@Timothy Elder can you provide some details around how we’ve got the deployment setup?

Give me a minute and I'll post up the service configs

ah yeah looks like dagit and dagster daemon have different working directories -- do you have a workspace file set up? you'll want to point the daemon and dagit at the same workspace file with

<command> -w path/to/workspace.yaml

.

yeah our

workspace.yaml

is in the dagit working directory

nice -- then

/home/ubuntu/.local/bin/dagster-daemon run -w /opt/dagster/FTS_Data_Science/dagster-jobs/workspace.yaml

should do the trick for you

@owen We don't start the Daemon from the command line directly, we use systemd to manage it. Is there something we can add to the service file in that gist that would be the equivelent? Also is that going to interfere with that Dagster daemon seeing the dagster.yml config file?

to be more specific, I was recommending updating

[Service]
Type=simple
User=ubuntu
Restart=always
WorkingDirectory=/opt/dagster
ExecStart=/home/ubuntu/.local/bin/dagster-daemon run
Environment="PATH=/home/ubuntu/.local/bin"
Environment="DAGSTER_HOME=/opt/dagster"
Environment="PATH=/usr/bin

to

[Service]
Type=simple
User=ubuntu
Restart=always
WorkingDirectory=/opt/dagster
ExecStart=/home/ubuntu/.local/bin/dagster-daemon run -w /opt/dagster/FTS_Data_Science/dagster-jobs/workspace.yaml
Environment="PATH=/home/ubuntu/.local/bin"
Environment="DAGSTER_HOME=/opt/dagster"
Environment="PATH=/usr/bin

thanks @owen we’re up and running!