New RunLLM response generated: >>>*# Question* Hi team.. I’ve set up a failure node on my workflow following the instructions here. However when I actually try to launch the workflow i see an error for the task defined for “on_failure”. I do see that the task was actually packaged, published and registered (flytekit 1.11)

Packaging flyte.workflows.mywf.my_failure_task -> 059_flyte.workflows.mywf.my_failure_task_1.pb

AND

/tmp/register4030374023/059_flyte.workflows.mywf.my_failure_task_1.pb                                            | Success | Successfully registered file |

When I actually try to launch the wf from Flyte UI, I see this…

Request failed with status code 500 Collected Errors: 1 Error 0: Code: TaskReferenceNotFound, Node Id: fn0, Description: Referenced Task [resource_type:TASK project:"myproj" domain:"production" name:"flyte.workflows.mywf.my_failure_task" version:"some_git_sha" ] not found.

# Answer The error you're encountering (

TaskReferenceNotFound

) when using

flytekit

version 1.11.0 or higher is likely due to changes in how tasks and workflows are registered and referenced in newer versions. This issue can be related to the module resolution and task registration process. According to this GitHub issue, Flytekit versions after 0.32.0 handle module names differently, which might be causing the

TaskReferenceNotFound

error. Additionally, this discussion suggests that the task resolver might be confused about the task's location. Would you like more detailed steps or further assistance? Sources: - Flyte Issue on TaskReferenceNotFound - Flyte Discussion on Task Resolver Slack Link https://.slack.com/archives/CP2HDHKE1/p1728021301.952159 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.