Unrelated issue: this morning, tried to restart a ...
# ask-communityb
Ben Ayers-Glassey
09/27/2022, 3:37 AMUnrelated issue: this morning, tried to restart a 4-day-old flow run which had some failed tasks, it changed some of the task runs from "Failed" to "Pending", but they've been pending all day and aren't running. Is there something else I need to do? Other team members have recalled this always being the case in the past when they've tried to use the Restart feature as well. 🤔
j
James Sopkin
09/27/2022, 3:16 PMQuick question- are you running on prefect 1 or prefect 2? Edit- I just noticed your previous thread referencing the GraphQl API, so I'm assuming Prefect 1
James Sopkin
09/27/2022, 3:18 PMAlso, it may be the case that when restarting a flow from failed tasks, that the tasks will fail or get hung up if they depend on upstream tasks
James Sopkin
09/27/2022, 3:21 PMIf that is the case, it may be worthwhile to use output caching https://docs-v1.prefect.io/core/concepts/persistence.html
b
Ben Ayers-Glassey
09/27/2022, 9:45 PM@James Sopkin It's prefect 1. (Might be good to have separate channels for v1 and v2!..)
Ben Ayers-Glassey
09/27/2022, 9:46 PMAlso, regarding caching, I should perhaps have mentioned that we're already using
flow.result = GCSResult(...)Ben Ayers-Glassey
09/28/2022, 4:16 AMMaybe this is relevant:
https://github.com/PrefectHQ/prefect/issues/5170
...but for now, we've just basically given up on Prefect's "restart failed tasks" feature, and will start to design our flows around the idea of getting as many good inputs through the ETL pipeline as possible, instead of crashing the entire flow.
👍 1
4 Views