Chris White

We are currently looking into what changes we would need to make for this setup to be simplified; as @tchar speculated, [`PREFECT_API_SSL_CERT_FILE` does default to `SSL_CERT_FILE`](https://github.com/PrefectHQ/prefect/blob/c7a2ec80d5a02e810a11c7f31df1f0ddc7401ce7/src/prefect/settings/models/api.py#L36). It seems that to...

I would love to make support for entrypoints specified as modules more prominent. It looks like `from_source` has [this line](https://github.com/PrefectHQ/prefect/blob/main/src/prefect/flows.py#L1344) that is causing the particular failure @mblarsen is seeing. I'm...

~~So there is one thing that could be happening here - right now the logic only deletes _auto-scheduled_ runs, so any run generated manually would be left hanging. I'll look...

Hi @Samreay - [this PR](https://github.com/PrefectHQ/prefect/pull/17313) should get released this week and will prevent the worker from crash-looping by cancelling runs associated with deleted deployments.

Thank you for debugging this and submitting a PR @lelouvincx! I'm surprised to see that `flow_run.state is None` there but either way your fix should do the trick!

Assuming you are trying to set no pull steps, you can avoid this by setting `pull: {}`; we can probably update the `DeploymentUpdate` schema to account for this also.

oh sorry I meant `pull: []` @masonmenges

How are you both creating deployments that produce this error? I can't reproduce and our code usually applies default pull steps.

@leesavoie-voltaiq I'm having trouble reproducing - if I kill my worker with CTRL+C, I get the same `Crashed` state as if I killed a served flow with CTRL+C; what signal...

@wangxing-git that is very helpful thank you!