The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

cap predict schedule.png

Hey all, is there an easy way to debug schedule execution errors? I got this error out of nowhere today (the image). But nothing has changed for that schedule or the execution.

Here's the code:
```@schedule(
    cron_schedule="0 8 * * *",
    pipeline_name="predict",
    execution_timezone="US/Pacific",
    mode="production",
)
def cap_predict_schedule():
    return get_namespace_definition(configs=["predict.yaml"]).run_config```

I have another schedule in the same schedule file that is also failing from this

Hey Kirk - schedules take an optional context arg, stick an unused argument in your function and it should work.

The mystery is why it would break suddenly - did you recently change dagster versions possibly?

Nope I haven't, I recently added logging to s3 which would have had me reapply the dagster application. The only other change to my user code was adding two more pipelines. I'm running v0.11.12 fwiw so it could be something there. Hopefully updating soon

<@U016C4E5CP8> Looks like that fixed it, not sure why it would have broken in the first place but thanks!