langchain-ai/langgraphjs
1
0
Fork 0
mirror of https://github.com/langchain-ai/langgraphjs.git synced 2026-07-23 01:26:57 -04:00
Code Issues 108 Packages Projects Releases 20 Wiki Activity

feature useStream: messages faulty update after interrupt #282

New Issue
Closed
opened 2026-02-15 18:15:28 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 18:15:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @OfirTeneJuno on GitHub (Jun 10, 2025).

Messages Update Issues After Interrupt Event Changes

Problem Description

After the changes introduced in PR #1244 that modified interrupt events to send interrupt data as values events instead of update events, there are issues with message updates following interrupt events.

Root Cause

  1. Missing Graph State: The interrupt data does not includes the graph state information
  2. Nested Structure: The interrupt values are now nested within the interrupt data structure
  3. Empty Messages: These changes cause the getMessages() function to return an empty array after each interrupt event

Impact

  • getMessages() function fails to retrieve messages after interrupt events
  • Message continuity is broken following interrupts
  • Potential data loss or incomplete message handling

Related

  • PR #1244: Changed interrupt event type from update to values

Expected Behavior

  • getMessages() should continue to work correctly after interrupt events
  • Graph state should be preserved or accessible through interrupt data
  • Message history should remain intact across interrupt boundaries

Actual Behavior

  • getMessages() returns empty array after interrupt events
  • Graph state is not available in interrupt data
  • Message continuity is broken
Originally created by @OfirTeneJuno on GitHub (Jun 10, 2025). # Messages Update Issues After Interrupt Event Changes ## Problem Description After the changes introduced in PR #1244 that modified interrupt events to send interrupt data as `values` events instead of `update` events, there are issues with message updates following interrupt events. ## Root Cause 1. **Missing Graph State**: The interrupt data does not includes the graph state information 2. **Nested Structure**: The interrupt values are now nested within the interrupt data structure 3. **Empty Messages**: These changes cause the `getMessages()` function to return an empty array after each interrupt event ## Impact - `getMessages()` function fails to retrieve messages after interrupt events - Message continuity is broken following interrupts - Potential data loss or incomplete message handling ## Related - PR #1244: Changed interrupt event type from `update` to `values` ## Expected Behavior - `getMessages()` should continue to work correctly after interrupt events - Graph state should be preserved or accessible through interrupt data - Message history should remain intact across interrupt boundaries ## Actual Behavior - `getMessages()` returns empty array after interrupt events - Graph state is not available in interrupt data - Message continuity is broken
yindo closed this issue 2026-02-15 18:15:28 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
checkpointer
docs-needed
documentation
enhancement
good first issue
good writeup
help wanted
invalid
langgraph-supervisor
open-swe-auto
platform
prebuilt
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraphjs#282
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?