Repository navigation
Bug with UI link to forked app with partition key #518
Description
When an application is forked and uses a partition key, the link in the UI does not have that partition key in the URL.
Current behavior
E.g. creating an app like this:
forked_app = (
ApplicationBuilder()
.with_graph(base_graph) # this could be different...
.initialize_from(
tracker,
resume_at_next_action=True,
default_state={"chat_history": []},
default_entrypoint="prompt",
fork_from_app_id=app_id,
fork_from_sequence_id=sequence_id,
fork_from_partition_key=partition_key
)
.with_identifiers(partition_key=partition_key)
.with_tracker(tracker, use_otel_tracing=True)
.build()
)Results in:
The links here are missing the partition key:
Activity
elijahbenizzy commentedon Feb 25, 2025
Hard to reproduce -- seems to work in some cases and not in others. See #519 -- that has a fix for part but not all of this.
andreahlert commentedon Mar 18, 2026
Took me about 50 min on this one hahaha. Turns out the bug only shows up when you explicitly use a partition_key on the fork. Without it (which is like 99% of the examples), the
nullinchildren.jsonlaccidentally matches the route and everything looks fine. So the bug was hiding in plain sight, just needed someone stubborn enough to keep forking with partition keys. PR incoming.fix: pass partition_key to child PointerModel in fork/spawn relations…
fix: pass partition_key to child PointerModel in fork/spawn relations…