Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When a flow has no storage attached, the agent should mark the run as failed #1395

Closed
jlowin opened this issue Aug 23, 2019 · 0 comments · Fixed by #1729
Closed

When a flow has no storage attached, the agent should mark the run as failed #1395

jlowin opened this issue Aug 23, 2019 · 0 comments · Fixed by #1729
Assignees
@joshmeek

Comments

@jlowin
Copy link
Member

jlowin commented Aug 23, 2019

It appears that if the Agent picks up a run with no storage, it will mark it as submitted. This run will then exist in limbo forever, as it can never be run. The agent should put it in a failed state if it can recognize it'll never run.
@jlowin jlowin added the bug Something isn't working label Aug 23, 2019
@joshmeek joshmeek self-assigned this Aug 23, 2019
@joshmeek joshmeek removed their assignment Sep 17, 2019
@joshmeek joshmeek added discussion and removed bug Something isn't working labels Sep 17, 2019
@joshmeek joshmeek self-assigned this Sep 24, 2019
@cicdw cicdw mentioned this issue Nov 12, 2019
Merged
3 tasks
abrookins pushed a commit that referenced this issue Mar 15, 2022
@marichka-offen
Merge pull request #1395 from PrefectHQ/update-orion-design
b659300 
Admin: Bumping orion-design version to 0.1.55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joshmeek joshmeek

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Proactively fail flow runs if there is an issue with flows storage PrefectHQ/prefect
2 participants
@jlowin @joshmeek