New RunLLM response generated: >>>*# Question* Hi! I'm seeing a very weird error when trying to use two different notebook tasks in a pipeline. It looks like only one is properly resolved, as throws an error regarding inputs not adhering to the types for the first task. Anybody had the same issues? # Answer It seems like you might be encountering an issue related to the use of

NotebookTask

within a Flyte pipeline. This is a known issue when using

NotebookTask

with

map_task

or chaining multiple notebook tasks. According to this discussion,

NotebookTask

was initially not supported with

map_task

, but support was added later. To help diagnose and resolve your issue, could you provide more details on the following: 1. The specific error message you are encountering. 2. A snippet of your workflow code where you are using the notebook tasks. 3. The versions of Flyte and Flytekit you are using. This information will help in providing a more accurate solution. If you are using an older version of Flytekit, consider updating to the latest version as the issue might have been resolved in a newer release. Would you like more detailed guidance on how to structure your workflow with multiple

NotebookTask

instances? Sources: - this discussion Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1722459299.838309 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.