New RunLLM response generated: >>>*# Question* Hi all -- has anyone used

dynamic

workflows in combination with reference launchplans (and specifically, the

{{ registration.version }}

macro)? We're observing an issue where it doesn't seem like the macro is getting properly replaced, and I'm wondering if the runtime nature of the dynamic workflow is the underlying cause (i.e., a "classic" workflow gets evaluated at registration time and thus the macro gets replaced properly, but because dynamic workflows skip that step, the macro never gets evaluated)? # Answer The

{{ registration.version }}

macro is populated by

flytectl register

during registration, and it is generally unnecessary for reference launch plans as it is preferable to bind to a specific version of the task or launch plan. However, dynamic workflows are evaluated at runtime, which might be causing the macro not to be replaced properly. According to the Flyte documentation, reference launch plans cannot be run locally and must be mocked out. This might be contributing to the issue you're observing with the

{{ registration.version }}

macro in dynamic workflows. Would you like more details on how to handle this situation or alternative approaches? Sources: - Reference launch plans - Flyte Slack Link https://.slack.com/archives/CP2HDHKE1/p1727737913.439859 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.