New RunLLM response generated: >>>*# Question* 👋 Hi Flyte community!! I am seeing a weird behavior with pyflyte register with --non-fast. It says

Successfully registered 5 entities

but actually skips to register Tasks. On workflow execution it uses old task code. Is this a known issue? Do we know the fix?

Successfully serialized 5 flyte objects
[DEBUG][selector_events.py:54] Using selector: EpollSelector
[x] Registration <task_name> type TASK skipped!
[✔] Registration <wf_name> type WORKFLOW successful with version 18c812f241-dirty
[✔] Registration <wf_name> type LAUNCH_PLAN successful with version 18c812f241-dirty
[✔] Registration <lp_name> type LAUNCH_PLAN successful with version 18c812f241-dirty
[✔] Registration <lp_name> type LAUNCH_PLAN successful with version 18c812f241-dirty
Successfully registered 5 entities

Thanks in advance!! # Answer The issue you're experiencing with

pyflyte register --non-fast

skipping task registration might be related to how Flyte handles task registration and versioning. According to this GitHub issue, Flyte automatically creates a default launch plan for workflows, which might lead to confusion if tasks are not explicitly registered or if there are versioning conflicts. Would you like more details on how to ensure tasks are registered correctly, or how to troubleshoot this issue further? Sources: - GitHub Issue 5073 Slack Link https://.slack.com/archives/CP2HDHKE1/p1730845177.664769 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.