Skip to content

Conversation

adk-bot
Copy link
Collaborator

@adk-bot adk-bot commented Oct 9, 2025

This PR adds documentation for the new pause and resume invocation feature, as requested in issue #744.

* **CPU-Bound Work:** Purely CPU-intensive synchronous tasks will still block their execution thread in both environments.

Understanding these behaviors helps you write more robust ADK applications and debug issues related to state consistency, streaming updates, and asynchronous execution.
### Pausing and Resuming Invocations
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this information is in the right general topic area, it doesn't fit with the rest of the content in this doc, making this information hard to find. In addition, the changes are not specific and technical enough to enable a developer to use the Resume feature.


When using a `LongRunningFunctionTool`, your function can initiate the long-running operation and optionally return an **initial result**, such as a long-running operation id. Once a long running function tool is invoked the agent runner pauses the agent run and lets the agent client to decide whether to continue or wait until the long-running operation finishes. The agent client can query the progress of the long-running operation and send back an intermediate or final response. The agent can then continue with other tasks. An example is the human-in-the-loop scenario where the agent needs human approval before proceeding with a task.

### Pause and Resume Mechanism
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LongRunningFunctions are not the focus of the Resume feature, as such these doc change recommendations are off the mark and possibly misleading.

@joefernandez
Copy link
Collaborator

DECISION: REJECT

  • Recommended updates are off the mark and need to be re-written from scratch
  • Creating new, separate PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants