Skip to content

V2: preserve pending QuestionV2 replies across server restart #52212

Closed as duplicate

Description

@gcomneno

Description

Focused Question-only slice of #36347.

A pending QuestionV2 request is process-local. After rebuilding the runtime graph against the same SQLite database, the Session survives but the pending question is no longer listed or replyable under its original request ID.

This issue intentionally covers only durable Question reply recovery. Permission durability and the broader parked/waiting continuation design remain tracked in #36347.

Plugins

None.

OpenCode version

Current dev.

Steps to reproduce

  1. Start a Session that blocks on the built-in question tool.
  2. Tear down the runtime/location graph while preserving the database.
  3. Build a fresh runtime graph using the same database and Location.
  4. List pending questions.
  5. Observe that the original pending Question is no longer available for reply.

Expected: the same request ID remains discoverable and replyable, and answering it can continue the Session without replaying the original provider turn or question tool execution.

Screenshot and/or share link

Not applicable.

Operating System

Ubuntu 24.04.

Terminal

GNOME Terminal.

Activity

  1. github-actions commented on Sep 30, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    • #36347: tracks preserving V2 permission and question waits across server restart, including durable question reply recovery.
    • #36585: reports pending forms remaining visible but unanswerable after managed-service restart.
  2. neriousy commented on Oct 20, 2026

    @neriousy
    Member

    Thanks for the focused reproduction showing that the session survives but its pending question disappears after restart. This is the same problem as #36347, where we're tracking preserving the original question and continuing safely; please subscribe there or add your fresh-runtime reproduction details.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions