nate nowack

hi @carlosjourdan - thanks for the issue I think there are a couple things here - I dont think its necessary / appropriate to use our low level callback util...

hi @carlosjourdan - let me look into that `Event loop is closed`. I don't remember seeing that but I will see if I can reproduce

hi @carlosjourdan - thanks for the context! I have [reproduced](https://github.com/zzstoatzz/prefect-monorepo/actions/runs/8886878310) this specifically on older python in windows I will add this issue to the backlog. We are doing work to...

hi @carlosjourdan - thanks for the issue! there are a couple things about this example code that you could try updating - i would use `get_client()` to get a client...

hi @povisenko - thanks for the issue this should be fixed by #13190 and released soon.

we should be able to edit the old data migration directly [here](https://github.com/PrefectHQ/prefect/blob/main/src/prefect/server/database/migrations/versions/postgresql/2023_01_31_110543_f98ae6d8e2cc_work_queue_data_migration.py) (for both sqlite and pg)

hi @hainenber - thanks for the PR! there seems to be some sneaky [issue](https://github.com/PrefectHQ/prefect/actions/runs/8618322937/job/23621415695?pr=12623) somehow related to pydantic 2 on newer python versions. I'm not sure how this relates to...

> @zzstoatzz What do you think about incorporating this behavior into the existing steps? That way users get caching with no changes needed. We could have the caching behavior be...

hi @maitlandmarshall - this makes a lot of sense! I've added this to the backlog

hi @santiagomlorenzo - thank you for the issue! hmm I'm yet to see this issue using the following flow to reproduce (based on your description) ```python from prefect import flow...