Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Runner drops callbackContextData written in onUserMessageCallback when it resumes an invocation

Abierto Apto para principiantes
  • ¿Algo no está bien?
#1,695 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@hirematha ya está trabajando en esto.

Desde el 26/10/2026.

  • #1696 de @svetanis — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java
Área
backend

Línea de trabajo

Lee runResumedAgent, resumeCore y runAgentWithUpdatedSession en la implementación de Runner. Sigue cómo se construye initialContext y se pasa a los callbacks; después, compara la ruta de reanudación con la ruta de una nueva invocación. Reproduce el problema con la capacidad de reanudación habilitada y un plugin que almacene datos en onUserMessageCallback; el trabajo estará terminado cuando los callbacks del agente reanudado vean esos datos y una prueba de regresión cubra el comportamiento de reanudación existente.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

needs review

Please make sure you read the contribution guide and file the issues in the right place.
Contribution guide.

🔴 Required Information

Describe the Bug

InvocationContext.callbackContextData() is "a map for storing temporary context data that can be shared
between different parts of the invocation", and InvocationContext.Builder passes the same instance to every
copy "so that Plugins can access the same data … across all types of callbacks."

A new invocation keeps that promise. runNewInvocation runs onUserMessageCallback on initialContext, and
runAgentWithUpdatedSession builds the agent's context with initialContext.toBuilder(), so the map is shared.

A resumed invocation does not. resumeCore runs onUserMessageCallback on its own initialContext, but
runResumedAgent is not given that context and builds the agent's from a second builder:

// runResumedAgent
InvocationContext rootContext =
    newInvocationContextBuilder(session, rootAgent)
        .invocationId(resolvedInvocationId)
        .runConfig(runConfig)
        .userContent(userContentFor(session, resolvedInvocationId, userContent))
        .build();

newInvocationContextBuilder starts a new, empty callbackContextData, so whatever a plugin stored in
onUserMessageCallback is missing from beforeRunCallback and from every callback that runs with the agent.
The same builder also resets endInvocation: a plugin that ends the invocation in onUserMessageCallback stops
a new invocation, but a resumed one still calls the model. On every resume, onRunErrorCallback also runs on
initialContext, so it does not see what beforeRunCallback stored, even when no new message is sent.

Trigger: resumability enabled and an invocation paused (for example on a long-running tool) that is then
resumed, with or without a new message. New invocations are unaffected.

Steps to Reproduce
  1. A Runner with ResumabilityConfig.builder().resumable(true), an LlmAgent with a long-running tool, and a
    plugin whose onUserMessageCallback puts a value into invocationContext.callbackContextData() and whose
    beforeAgentCallback reads it back.
  2. Send a message. The model calls the tool and the invocation pauses.
  3. Send the tool's function response, which resumes the invocation.
Expected Behavior

On the resumed turn, beforeAgentCallback reads the value that turn's onUserMessageCallback stored, as it
does on the first turn.

Observed Behavior

The first turn reads its value, and the resumed turn reads null (the plugin stores message-1, then
message-2). beforeAgentCallback reads, per turn:

[agent:message-1, agent:null]

The same happens when the resume is routed to a sub-agent instead of the root.

Environment Details
  • ADK Library Version: main @ 84bae34a (pom 1.13.0)
  • OS: not OS-specific
  • TS Version: N/A (Java)
Model Information

N/A

🟡 Optional Information

Regression

No. Present since resuming an invocation was added (v1.11.0).

Willingness to contribute

Yes, a PR follows. runResumedAgent takes initialContext and builds the agent's context with
initialContext.toBuilder(), as runAgentWithUpdatedSession does:

InvocationContext rootContext =
    initialContext.toBuilder()
        .agent(rootAgent)
        .userContent(...)
        .build();
How often has this issue occurred?

Always (100%), on a resumed invocation.

Lenguaje dominante
Java
Estrellas
1.8k
Forks
440
Merge medio
3 d 16 h
PR fusionados (30 d)
92

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de google/adk-java

Todos los issues de google/adk-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.