Just wondering if anyone has seen this in Prefect Server, we accidentally trigger the flow for the wrong date and when we try to cancel the flow from the UI it didn't work.
The task continue to run under the Dask and we were not able to stop that task until we restart the Dask.
Would appreciate if anyone know how to fix this without restarting the Dask?
k
Kevin Kho
11/18/2021, 7:22 PM
Hey @Vipul so both Cloud and Server, cancellations are a best effort thing and cancelling things on a different Python process such as Dask is very hard so this is expected behavior.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.