Cannot plot multiple graphs using plotly in for loop

[Harshal12355]

Is your feature request related to a problem? Please describe.

Yes. When trying to generate multiple Plotly graphs in a loop—e.g., comparing one feature against a list of others—you’re required to manually assign a unique id to each graph. This requirement isn’t mentioned in the documentation, and without it, the function doesn’t work as expected. This makes it difficult to automate plotting in batch.

Describe the solution you'd like

The function should automatically assign unique ids (e.g., using uuid or hash values) when generating multiple plots. Alternatively, the documentation should clearly state that a unique id must be provided when plotting dynamically.

Describe alternatives you've considered

I’ve worked around this by generating uuids manually for each graph (enumerating through the list), but it’s not ideal for workflows with many plots. Especially if you do this for multiple plots, they are bound conflict at different parts of the code base.

Additional context

This issue significantly limits the usability of the function for dynamic or large-scale plotting. Automating id assignment or improving the docs would greatly improve the developer experience.

[shivam-singhal]

@BloggerBust I think this might interest you!

@Harshal12355 we are working on fixing this soon!

[BloggerBust]

Thanks so much for raising this, @Harshal12355!

You’re absolutely right that dynamically generated components in loops require a manual workaround to avoid ID collisions, and the behavior isn’t clearly documented.

We’ve addressed this in PR #712, which introduces a new reactive runtime with AST-based analysis and DAG-driven reruns. Components are now automatically assigned stable identifiers to ensure consistent behavior and in dynamic contexts, you can provide your own identifier that will be hashed as part of the stable identifier:

for i in range(3):
    text(f"Item {i}", identifier=f"text-{i}")

📄 See the updated docs

This ensures stable component IDs and atom names even in loops, which avoids collisions and preserves reactivity.

Appreciate you flagging this! Let us know if you hit any other rough edges.