Nick Hoffmann
04/22/2024, 3:16 PM- name: PREFECT_WORKER_PREFETCH_SECONDS
value: "30"
- name: PREFECT_WORKER_QUERY_SECONDS
value: "5"
This works perfectly fine for all auto-generated scheduled flow runs, but when we try to manually kick off a run starting "now" the worker doesn't actually end up making a kubernetes Job for the run. The flow run is then permanently stuck in "Pending" and has no logs, when I would expect at least the worker logs of
Worker 'KubernetesWorker <id>' submitting flow run '<flow run id>'
Creating Kubernetes job...
Completed submission of flow run '<flow run id>'
Job '<job id>': Pod has status 'Pending'.
Manually-triggered flow runs do work if I select start "later" and set 1 minute in the future, rather than "now". any ideas?