Scheduler does not seem to run on a schedule

[webb-ben]

Description:

The Scheduler software is not executing jobs as expected on its defined schedule. It only runs when triggered manually, whereas it should automatically crawl all partitions as needed based on the configured schedule.

Expected Behavior:

The Scheduler should automatically trigger and execute jobs according to the defined schedule without manual intervention.

[C-Loftus]

For Andrew / future reference, the schedule needs to be manually enabled in the UI so the entire crawl is not run in development

[webb-ben]

Note I enabled the schedule in the UI but when I checked, there was a failure to run:

dagster._core.errors.ScheduleExecutionError: Error occurred during the evaluation of schedule crawl_entire_graph_schedule

  File "/usr/local/lib/python3.10/site-packages/dagster/_grpc/impl.py", line 344, in get_external_schedule_execution
    return schedule_def.evaluate_tick(schedule_context)
  File "/usr/local/lib/python3.10/site-packages/dagster/_core/definitions/schedule_definition.py", line 959, in evaluate_tick
    result = list(ensure_gen(execution_fn(context)))
  File "/usr/local/lib/python3.10/site-packages/dagster/_core/definitions/decorators/schedule_decorator.py", line 153, in _wrapped_fn
    with user_code_error_boundary(
  File "/usr/local/lib/python3.10/contextlib.py", line 153, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/usr/local/lib/python3.10/site-packages/dagster/_core/errors.py", line 297, in user_code_error_boundary
    raise new_error from e

The above exception was caused by the following exception:
dagster._check.functions.CheckError: Failure condition: The instance is not available to load partitions. You may be seeing this error when using dynamic partitions with a version of dagster-webserver or dagster-cloud that is older than 1.1.18. The other possibility is that an internal framework error where a dynamic partitions store was not properly threaded down a call stack.

  File "/usr/local/lib/python3.10/site-packages/dagster/_core/errors.py", line 287, in user_code_error_boundary
    yield
  File "/usr/local/lib/python3.10/site-packages/dagster/_core/definitions/decorators/schedule_decorator.py", line 181, in _wrapped_fn
    yield from cast(RunRequestIterator, ensure_gen(result))
  File "/opt/dagster/app/userCode/main.py", line 478, in crawl_entire_graph_schedule
    for partition_key in sources_partitions_def.get_partition_keys():
  File "/usr/local/lib/python3.10/site-packages/dagster/_core/definitions/partition.py", line 533, in get_partition_keys
    check.failed(
  File "/usr/local/lib/python3.10/site-packages/dagster/_check/functions.py", line 1704, in failed
    raise CheckError(f"Failure condition: {desc}")

[C-Loftus]

I remember I ran into this with Oregon. I believe this is due to us not passing in the current dagster instance for the instance= argument somewhere. Or not having set the dagster home env var. The error message regarding using an old version of the web server I believe is incorrect and there is an open PR to make it more specific.

dagster-io/dagster#17664 (comment)