I'm still stuck on displaying decks from a task that is fanned-out using map_task. I've found a git issue from 2023 saying this was going to be a supported issue and another user in the community messaged me saying this should work. However, after enabling decks in both the

@task(..., enable_deck=True)

and

map_task(my_function, concurrency=some_number, enable_deck=True)

, my tasks generated using map_task still don't show a Deck button to show rendered outputs for each deck. I re-worked my code to remove other complexities like @dynamic workflows and use of functools to define constant paramenters, but even when defining a @workflow that calls map_task(task_function), the Decks don't show up in Flyte UI. Do I have to return Deck object from the mapped task in order to get it to show up in the Flyte Dashboard? Is there another way to access the Decks from each of these mapped tasks that's not through the executed workflow(e.g. some kubernetes hack, another place in the Flyte UI)? Is there something I need to consider/add in the Flyte helm configuration file?

It is very hard to do this in v1. this is because v1 map tasks state are stored in etcd, which is 1.5MBs storing deck links is very hard

Forgot to reply to this, thanks for the explanation and workaround!