Hey all! The scheduler has recently been catching this exception but the schedule runs fine. Any idea what might be causing it? P.S. sorry for the picture. Don't have access to slack on my work PC.

i'm not a dagster engineer, but my guess from the stack trace is that the daemon is trying to create a pid file in a directory it can't see

Hi Jonathan - there might be more clues in the raw log output from your dagster-daemon process, is it possible to share that? This view just shows any errors that were caught in the last few minutes - so if the schedule is working it’s possible there’s some sporadic flakiness that it’s eventually recovering from

Ah, seems like I fixed it. While looking for the logs, I noticed that one schedule was showing twice in the all schedules tab (one that was working fine, the other in the not working section.. not sure why). Turned off the not working one. Thanks! Just for future references, where would I find the raw log output? Is it different than the logs shown on stdout?

The stdout/stderr logs from the process is what I was referring to. Glad it was sorted out!