Problemsby GlyphPrefect lock-in makes switching costly
2 posts from 2 people2d activeSteady, +1 this weekunverified
Posts per day
The posts behind it
Resuming a blocking pause counts as a new run, so a flow with retries that paused once is not retried
### Bug summary A flow with `retries=1` that calls `pause_flow_run()` (or `wait_for_input`) and then fails after being resumed is not retried. Resuming the pause increments `flow_run.run_count`, so when the flow fails `RetryFailedFlows` sees `run_count (2) > retries (1)` and...
Restore advisory Cloud API compatibility checks on pull requests
The OSS Cloud API compatibility workflow is disabled, so API changes can merge before the corresponding changes reach Prefect Cloud. This can break the compatibility tests downstream. Restore the shared suite as a non-blocking check. Compare the base and proposed changes against...
Companies and products named
About this problem
Evidence
2 posts from 2 people in 1 place, about 1 a week over 15 days. Mostly on PrefectHQ/prefect.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "vendor-lock" rule about Prefect. First post Oct 27, 2026, latest Nov 10, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
Vendor lock-in makes switching tools costly
17 posts from 17 people on GitHub issues, Hacker News, Reddit.
Claude Code lock-in makes switching costly
14 posts from 14 people on GitHub issues, Hacker News, Reddit.
Kubernetes lock-in makes switching costly
13 posts from 10 people on GitHub issues.
GitHub lock-in makes switching costly
12 posts from 11 people on GitHub issues.
Claude lock-in makes switching costly
10 posts from 10 people on GitHub issues, Hacker News, Reddit.
ChatGPT lock-in makes switching costly
6 posts from 6 people on GitHub issues, Reddit, Hacker News.
NVIDIA lock-in makes switching costly
5 posts from 5 people on GitHub issues, Hacker News, Bluesky.
Codex lock-in makes switching costly
5 posts from 5 people on GitHub issues.
PyTorch lock-in makes switching costly
4 posts from 4 people on GitHub issues.
LlamaIndex lock-in makes switching costly
3 posts from 3 people on GitHub issues.
llama.cpp lock-in makes switching costly
3 posts from 3 people on GitHub issues.
Anthropic lock-in makes switching costly
3 posts from 3 people on GitHub issues, Hacker News.
Other Prefect problems
Prefect users keep filing bugs
Top post: "V2 UI feedback: Bug or incorrect behavior", one of 24 posts from 19 people on GitHub issues.
Prefect upgrades break working setups
17 posts from 16 people on GitHub issues.
Trouble with Prefect flow
Top post: "Flow run graph polls graph-v2 every second for the whole run, rebuilding the full graph each time", one of 16 posts from 12 people on GitHub issues.
Trouble with Prefect deployment
Top post: "Worker crashes when reading the deployment fails with a non-404 error before submitting a run", one of 3 posts from 3 people on GitHub issues.
Prefect rate limits and usage caps block work
3 posts from 3 people on GitHub issues.
Trouble with Prefect missing
Top post: "V2 UI feedback: Missing feature - Filter by tags search box", one of 2 posts from 2 people on GitHub issues. Unverified.
Trouble with Prefect list
One post on GitHub issues: "hash_objects erases tuple/list and int/str-key distinctions, so task_input_hash serves stale cached results". Unverified.
Trouble with Prefect deployments
One post on GitHub issues: "(ui-v2) Quick Run from deployments list navigates away when selecting from enum dropdown". Unverified.
Trouble with Prefect crashes
One post on GitHub issues: "`Flow.serialize_parameters` crashes on errors other than `TypeError`/`ValueError`/`RecursionError` from". Unverified.
History