@ancient-wolf-19325 is there a conflict using

@dataclass_json

annotations on models used in

@dynamic

workflows?

Yes, there have been known issues when using

@dataclass_json

-annotated dataclasses with Flyte's

@dynamic

workflows, particularly with serialization and deserialization of nested dataclasses or types like

FlyteFile

and

FlyteDirectory

. For example, the

remote_source

attribute can be lost when passing such dataclasses from a

@dynamic

to a

@task

, and Flyte may fail to properly bind or convert dataclass fields, especially lists or complex types, leading to runtime errors or type mismatches. These issues have been reported and discussed in the Flyte community, and some have been addressed in recent versions, but not all edge cases may be fully resolved yet. See Flyte Issue #1938, Flyte Issue #4581, and Flyte Issue #5593. Would you like more detail on specific workarounds, affected versions, or best practices for using dataclasses in dynamic workflows? Sources: - https://github.com/flyteorg/flyte/issues/1938 - https://github.com/flyteorg/flyte/issues/4581 - Flyte Issue #5593 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

yes, explain workarounds and affected versions