Data and AI struggles

1,730 problems · 342 companies

Data engineering

Trouble with Prefect flow

14 posts from 11 people12d activeFading, +0 this week

Posts per day

Posts per day14 posts, Aug 28 to Nov 9

The posts behind it

GitHub issuesPrefectHQ/prefect · chuqCTCOct 30

Flow run stays Running forever when setup_run_context raises

### Bug summary If `setup_run_context()` raises, e.g. because the result storage block doesn't exist, the flow run is left `Running` forever. `initialize_run`'s `except Exception: raise` sets no state. It should crash the run, as the `BaseException` branch does. ### Version info...

1 replies
GitHub issuesPrefectHQ/prefect · chuqCTCOct 29

Task run recorder drops valid events when one event in a batch references a missing flow run

...batch fails. The failed events are retried together with new ones, so the bad event keeps failing later batches until valid events from other flow runs run out of retries and are dropped. As a result, task runs of healthy flow runs can be left without their final state, or never...

GitHub issuesPrefectHQ/prefect · chuqCTCOct 27

`POST /flow_runs/{id}/resume` returns 500 when `run_input` contains an integer outside the 64-bit range

### Bug summary Resuming a paused flow run returns 500 when `run_input` contains an integer outside the 64-bit range. The run stays `PAUSED` and no input is stored. #23429 fixes the same error in the flow run list endpoints, but doesn't change this one. Output: Server error:...

GitHub issuesPrefectHQ/prefect · markounikau-ultramarinOct 17

Flow run graph polls graph-v2 every second for the whole run, rebuilding the full graph each time

### Bug summary The flow run graph in the UI re-fetches `GET /flow_runs/{id}/graph-v2` every ~1 second for as long as the flow run is running. Each request rebuilds the full graph on the server. With a few browser tabs left open on long-running flow runs, this polling became the...

1 reactions1 replies
GitHub issuesPrefectHQ/prefect · pedroarruda07Oct 12

Flow rescheduled after SIGTERM skips previously triggered pause_flow_run calls

### Bug summary ### Description We encountered an issue where a Prefect flow using `pause_flow_run()` for mandatory human validations was rescheduled following a Kubernetes pod termination. On the new execution attempt, the flow restarted from the beginning but skipped both...

GitHub issuesPrefectHQ/prefect · rsundqvistOct 12

prefect flow-run execute exits 0 when the flow run crashes and the Crashed report fails, leaving the run Running forever

### Bug summary # `prefect flow-run execute` exits 0 when the flow run crashes and the `Crashed` report fails, leaving the run `Running` forever > Debugged and reproduced by Claude (Anthropic's Claude Code), from a production incident on our self-hosted > Prefect server. Repro...

1 replies
GitHub issuesPrefectHQ/prefect · digit50Oct 10

JSON flow result with a "data" or "result" key reads back wrong from the API

### Bug summary A flow with `result_serializer="json"` and persisted results that returns a dict containing a `data` or `result` key gets the wrong value back when the result is loaded from storage. `{"data": [1, 2, 3], "total": 3}` comes back as `[1, 2, 3]`, `{"result": 5,...

GitHub issuesPrefectHQ/prefect · digit50Oct 10

Breaking out of an async generator flow marks the run Failed after Completed

### Bug summary When I stop consuming an async generator flow early (`break` and then `aclose()`), the flow run is first set to `Completed` and then to `Failed` with `AttributeError: 'async_generator' object has no attribute 'throw'`. Both the `on_completion` and the...

GitHub issuesPrefectHQ/prefect · JonasFockstedtOct 8

UI v2: a flow run's artifacts can't be opened directly from the Artifacts tab or the run graph

### Bug summary In the V2 UI, the artifacts a flow run produced can no longer be opened directly from the flow run page. In the V1 UI, both of these went straight to the artifact. 1. **Artifacts tab:** clicking an artifact card with a key opens `/artifacts/key/ `, which lists...

1 reactions1 replies
GitHub issuesPrefectHQ/prefect · TheoMathurinSep 24

[UI] Open flow run on click in flow runs timeline

### Describe the current behavior Currently, it is possible to open a flow run by clicking on its name in the list of flow runs, below the flow runs plot. However, clicking on a flow run in the plot itself does nothing. ### Describe the proposed behavior It would be great to...

1 replies
GitHub issuesPrefectHQ/prefect · mgsnunoSep 17

Flow ends COMPLETED when it returns a list of .map() results containing a FAILED task (states nested one level are ignored)

### Bug summary A flow that returns a list containing the results of two or more `.map()` calls ends `COMPLETED` even when one of the mapped tasks `FAILED`. The same flow returning a flat list of the same futures ends `FAILED('1/2 states failed.')`. ### Cause...

GitHub issuesPrefectHQ/prefect · desertaxleSep 14

Add Quick Run and Custom Run to the flow's Deployments tab

### Current behavior In V2, the row menu on a flow's **Deployments** tab offers only **Copy ID**. Users must open a deployment's detail page to reach its Run menu, even though the global Deployments table already provides Quick Run and Custom Run actions. Adding those actions to...

1 replies
GitHub issuesPrefectHQ/prefect · shdxiangSep 2

V2 UI feedback: Difficult to move the cursor into the Flow Run tooltip

...the tooltip to show information for that neighboring run. As a result, it is very difficult to move the cursor into the tooltip and interact with its links. Expected behavior: The tooltip should remain open for the originally hovered flow run while the cursor moves toward or...

2 reactions
GitHub issuesPrefectHQ/prefect · TheUkrainian1991Aug 28

Dashboard deployment quick run flow run page renders in the Scheduled state and never updates

...the stuck tab also immediately shows the correct state, so this appears to be the page failing to poll / re-render rather than a server-side state problem. ### Reproduction 1. Open a deployment in the UI 2. Click "Quick run" 3. Click "View run" in the toast that appears 4....

Companies and products named

14 posts
2 posts
2 posts
1 post
1 post
About this problem

Evidence

14 posts from 11 people in 1 place, about 1 a week over 64 days. Mostly on PrefectHQ/prefect. Tools named alongside: Kubernetes, PostgreSQL, GitHub, Claude Code.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts about Prefect with no known issue, sharing the word "flow". First post Aug 28, 2026, latest Oct 30, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

Other Prefect problems

Prefect users keep filing bugs

Top post: "Preferred way to cite prefect", one of 20 posts from 17 people on GitHub issues.

Prefect upgrades break working setups

15 posts from 14 people on GitHub issues.

Trouble with Prefect deployment

Top post: "`prefect deployment delete --all` leaves deployments behind when there are more than 200", one of 2 posts from 2 people on GitHub issues. Unverified.

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.

Prefect rate limits and usage caps block work

2 posts from 2 people on GitHub issues. 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.

History

Momentum went from steady to fading.

Nov 6, 2026

Momentum went from rising to steady.

Nov 3, 2026

Momentum went from fading to rising.

Nov 2, 2026

Momentum went from steady to fading.

Oct 19, 2026

Momentum went from rising to steady.

Oct 17, 2026

Momentum went from fading to rising.

Oct 14, 2026

Momentum went from steady to fading.

Oct 2, 2026

First seen with 5 posts; the top post now: "Flow run graph polls graph-v2 every second for the whole run, rebuilding the full graph each time".

Sep 25, 2026