Introduces two major capabilities: - Workflow runtime: graph-based execution engine for composing deterministic execution flows for agentic apps, with support for routing, fan-out/fan-in, loops, retry, state management, dynamic nodes, human-in-the-loop, and nested workflows - Task API: structured agent-to-agent delegation with multi-turn task mode, single-turn controlled output, mixed delegation patterns, human-in-the-loop, and task agents as workflow nodes Co-Authored-By: Bo Yang <ybo@google.com> Co-Authored-By: George Weale <gweale@google.com> Co-Authored-By: Sean Zhou <seanzhougoogle@google.com> Co-Authored-By: Shangjie Chen <deanchen@google.com> Co-Authored-By: Swapnil Agarwal <swapnilag@google.com> Co-Authored-By: Wei Sun <weisun@google.com> Co-Authored-By: Xuan Yang <xygoogle@google.com> Co-Authored-By: Yifan Wang <wanyif@google.com> Change-Id: I35932c50cfe29ff68559e3781713dbb5eb7b3382
ADK Workflow Loop Self Sample
Overview
This sample demonstrates how a node can repeatedly loop back to itself based on a specific route condition in ADK Workflows.
It takes a user-provided target number (between 0 and 10), and uses a guess_number function to randomly generate guesses. If the guess is incorrect, the function yields a specific route (guessed_wrong). The workflow is configured such that this route directs the execution right back to the guess_number node, creating a loop that continues until the correct number is guessed.
In ADK Workflows, you can create self-referential loops or iterative processes by routing a node's output back to itself.
Sample Inputs
5010
Graph
[ START ]
|
v
[ validate_input ]
|
v
+->[ guess_number ]-----+
| | |
| v |
+--"guessed_wrong" v
(Loop ends when
guess is correct)
How To
-
From within your node (agent or function), yield a specific
Eventwith a route name when you determine the node needs to be executed again:def guess_number(target_number: int): # ... if guess != target_number: yield Event(route='guessed_wrong') -
In the
Workflowedges definition, create a conditional edge where the source and target are the same node, using a routing map dict:(guess_number, {'guessed_wrong': guess_number})