dv-pipecat-flows 0.0.22.dev1900__tar.gz → 0.0.22.dev2000__tar.gz

{dv_pipecat_flows-0.0.22.dev1900/src/dv_pipecat_flows.egg-info → dv_pipecat_flows-0.0.22.dev2000}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dv-pipecat-flows
-Version: 0.0.22.dev1900
+Version: 0.0.22.dev2000
 Summary: Conversation Flow management for Pipecat AI applications
 License: BSD 2-Clause License
 Project-URL: Source, https://github.com/pipecat-ai/pipecat-flows

{dv_pipecat_flows-0.0.22.dev1900 → dv_pipecat_flows-0.0.22.dev2000/src/dv_pipecat_flows.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dv-pipecat-flows
-Version: 0.0.22.dev1900
+Version: 0.0.22.dev2000
 Summary: Conversation Flow management for Pipecat AI applications
 License: BSD 2-Clause License
 Project-URL: Source, https://github.com/pipecat-ai/pipecat-flows

{dv_pipecat_flows-0.0.22.dev1900 → dv_pipecat_flows-0.0.22.dev2000}/src/pipecat_flows/manager.py

@@ -2075,22 +2075,69 @@ In all of these cases, you can provide a `name` in your new node's config for de
         previous_node_id = self._current_node
         router_pick = self._last_router_pick
         self._last_router_pick = None
+        # In v2 deterministic lowering, ``FlowConfig.nodes`` is keyed by
+        # ``node.name`` (see calling/flow_builder_v2.py:214), and
+        # ``self._current_node`` stores that same dict key — so
+        # ``previous_node_id`` IS the previous node's name. No lookup
+        # against ``self._nodes`` needed. Backend's
+        # ``tools/helper.py:build_tool_call_log_response`` matches these
+        # against ``AgentVersionNode.name → label`` to populate
+        # source_node_label / target_node_label for the FE pill.
         transition_tool_name = f"transition_to_{node_id}"
-        transition_args: Dict[str, Any] = {
-            "from_node_id": previous_node_id,
-            "to_node_id": node_id,
-        }
-        if router_pick:
-            transition_args.update(router_pick)
-        transition_call_id = await start_tracking(
-            transcript_handler=getattr(self, "_transcript_handler", None),
-            tool_name=transition_tool_name,
-            args=transition_args,
-            tool_phase="on_call",
-            tool_type="transition",
-            current_node=previous_node_id,
-            logger=logger,
-        )
+        transition_call_id: Optional[str] = None
+        # Skip the initial node entry — it's not a transition (no prior
+        # node) and the FE pill would render as "Unknown → X" with no
+        # useful information. Also skip in static-flow init paths where
+        # the engine briefly _set_nodes the same node twice during setup.
+        # Log atomically (start + complete back-to-back at the TOP of
+        # _set_node) so each entry always has executed_at set. Earlier
+        # design held the start_tracking call open until the bottom of
+        # _set_node, but in deep auto_transition chains (Speak→Router→
+        # Speak→End) the outer _set_node calls often never reach their
+        # complete_tracking because End's hangup tears down the call
+        # mid-chain — leaving stub entries with null status/latency/
+        # executed_at. Atomic logging makes every transition self-
+        # contained: zero risk of half-baked entries shipping to history.
+        if previous_node_id is not None and previous_node_id != node_id:
+            transition_args: Dict[str, Any] = {
+                "from_node_id": previous_node_id,
+                "to_node_id": node_id,
+                # FE pill key aliases consumed by CallTranscriptViewer.
+                "source_node": previous_node_id,
+                "target_node": node_id,
+            }
+            if router_pick:
+                transition_args.update(router_pick)
+            logger.info(
+                f"[node_transition] from={previous_node_id} to={node_id} "
+                f"router_pick={router_pick}"
+            )
+            transition_call_id = await start_tracking(
+                transcript_handler=getattr(self, "_transcript_handler", None),
+                tool_name=transition_tool_name,
+                args=transition_args,
+                tool_phase="on_call",
+                # `node_transition` matches the FE's filter in
+                # components/call-details/CallTranscriptViewer.tsx so this
+                # renders as a NodeTransitionDivider pill rather than a
+                # generic tool pill.
+                tool_type="node_transition",
+                current_node=previous_node_id,
+                logger=logger,
+            )
+            # Atomic completion right after start — see comment above.
+            await complete_tracking(
+                transcript_handler=getattr(self, "_transcript_handler", None),
+                function_call_id=transition_call_id,
+                tool_name=transition_tool_name,
+                function_start_time=transition_start_time,
+                response_data={
+                    "to_node_id": node_id,
+                    "from_node_id": previous_node_id,
+                },
+                status_code=200,
+                logger=logger,
+            )
 
         try:
             # Clear any pending transition state when starting a new node
@@ -2508,19 +2555,10 @@ In all of these cases, you can provide a `name` in your new node's config for de
 
             # node_entered observer is now emitted at the *top* of _set_node
             # so short-circuit paths (auto_transition / router-mode) get it too.
-
-            await complete_tracking(
-                transcript_handler=getattr(self, "_transcript_handler", None),
-                function_call_id=transition_call_id,
-                tool_name=transition_tool_name,
-                function_start_time=transition_start_time,
-                response_data={
-                    "to_node_id": node_id,
-                    "to_node_label": node_config.get("label"),
-                },
-                status_code=200,
-                logger=logger,
-            )
+            # Transition tool-log is also emitted atomically at the top of
+            # _set_node (right after `previous_node_id` capture) — no
+            # complete_tracking needed here, deferred completion was
+            # unreliable for outer nodes when the call ended mid-chain.
 
         except Exception as e:
             # If setup crashed inside an uninterruptible node, the guard is
@@ -2532,19 +2570,6 @@ In all of these cases, you can provide a `name` in your new node's config for de
             except Exception:
                 pass
             logger.error(f"Error setting node {node_id}: {str(e)}")
-            try:
-                await complete_tracking(
-                    transcript_handler=getattr(self, "_transcript_handler", None),
-                    function_call_id=transition_call_id,
-                    tool_name=transition_tool_name,
-                    function_start_time=transition_start_time,
-                    response_data=None,
-                    status_code=500,
-                    error_details={"error": str(e), "type": type(e).__name__},
-                    logger=logger,
-                )
-            except Exception as track_exc:
-                logger.warning(f"complete_tracking failed for {transition_tool_name}: {track_exc!r}")
             raise FlowError(f"Failed to set node {node_id}: {str(e)}") from e
 
     def _schedule_deferred_post_actions(self, post_actions: List[ActionConfig]) -> None: