Great question—here’s where to report it depending on what you’re seeing: - If it’s a Prefect Cloud–specific or workspace/account issue (e.g., schedules not triggering only in your Cloud workspace, UI oddities, incident-level impact): open a support ticket via the Help icon in Prefect Cloud or email support@prefect.io. - If it looks like a core scheduling/orchestration bug (e.g., schedule not enqueuing, work pool assignment logic, deployments/schedules behavior): open a GitHub issue in the Prefect repo: Prefect Issues. - If it’s clearly specific to the Kubernetes worker/integration (e.g., worker logs, pod templates, job creation failures): open an issue here: prefect-kubernetes Issues. Helpful details to include: - Prefect version and worker image/tag - Work pool type (Kubernetes) and worker logs - Deployment config (relevant `prefect.yaml`/`flow.from_source(...).deploy(...)` snippet), schedule definition, and timezone - Example flow run IDs, timestamps (UTC), and what you expected vs observed - Any relevant Kubernetes events/pod statuses If you share a quick summary here (what’s failing, versions, and a run ID), I can help you determine the best place to file it and suggest what to include.