New RunLLM response generated: >>>*# Question* I am using a custom type for my tasks and objects are being correctly passed between tasks/ workflows, as long as the container images have the custom type plugin installed. However, it starts to fail, once I using launchplans instead of workflows. I see errors such as

failed to launch workflow, caused by: rpc error: code = InvalidArgument desc = invalid aoi input wrong type. Expected simple:BINARY, but got simple:STRUCT

Why is that? Do i need to install the type plugin somewhere else (ie the propeller image used) so that I can use it with lauchplans, too? # Answer The error you're encountering suggests a type mismatch between what is expected and what is provided when using launch plans. This typically happens when the custom type plugin is not recognized or available in the environment where the launch plan is executed. According to Flyte documentation, custom types need to be registered and available in the Flyte environment where they are used. This means that the custom type plugin should be installed not only in the container images used for tasks but also in the Flyte backend components like FlytePropeller, which handles the execution of workflows and launch plans. Would you like more details on how to ensure the custom type plugin is available in the FlytePropeller environment? Sources: - Flyte documentation Slack Link https://flyte.slack.com/archives/CP2HDHKE1/p1732110610.186059 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.