Problemsby IbisTrouble with Prefect deployment
Data engineering2 posts from 2 people2d active+11 post in the last 7 days, 0 the 7 days before (steady)Unverified
Posts per day
The posts behind it
2, newest first`prefect deployment delete --all` leaves deployments behind when there are more than 200### Bug summary `prefect deployment delete --all` reads deployments with a single `read_deployments()` call. The API returns at most `PREFECT_SERVER_API_DEFAULT_LIMIT` (200 by default) results per request, so with more deployments than that the command deletes only the first...PrefectHQ/prefect · RaphaelFakhriOpen ↗Format V2 deployment Created and Updated timestamps for readability### Bug summary The V2 deployment detail page displays Created and Updated as raw API timestamp strings, such as `2026-09-14T14:57:45.535230Z`. These long values are harder to scan than the formatted dates shown in V1 and take up unnecessary space in the metadata sidebar. ###...PrefectHQ/prefect · desertaxleOpen ↗
Companies and products named
About this problem
Evidence
2 posts from 2 people in 1 place, about 1 a week over 35 days. Mostly on PrefectHQ/prefect. Tools named alongside: GitHub.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about Prefect with no known issue, sharing the word "deployment". First post Sep 14, 2026, latest Oct 18, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
Other Prefect problems
History
Trouble with Prefect deployment (2 posts)