filterDataParts() in AIV4Adapter strips data-* message parts on recall — breaks workflow suspension
WorkflowsAgentStorageTools
Package:
Summary:
When a workflow tool suspends during streaming, the frontend correctly receives
Root cause:
This creates an asymmetry between the save and recall paths:
- Save path:
- Recall path:
Note:
Reproduction steps:
1. Create an agent with a workflow tool that calls
2. Trigger the workflow via chat
3. Observe the streaming response — the assistant message includes a
4. Refresh the page
5. Observe the recalled message — the
@mastra/coreSummary:
When a workflow tool suspends during streaming, the frontend correctly receives
data-tool-call-suspendedrunIdtoolCallIdsuspendPayloadresumeSchemaRoot cause:
AIV4Adapter.toUIMessage()filterDataParts()"data-"This creates an asymmetry between the save and recall paths:
- Save path:
AIV5Adapter.fromUIMessage()data-*- Recall path:
AIV4Adapter.toUIMessage()filterDataParts()Note:
AIV5Adapter.toUIMessage()elseget.all.aiV4.ui()Reproduction steps:
1. Create an agent with a workflow tool that calls
suspend()2. Trigger the workflow via chat
3. Observe the streaming response — the assistant message includes a
data-tool-call-suspendedrunIdsuspendPayload4. Refresh the page
5. Observe the recalled message — the
data-tool-call-suspendedtool-workflow-*state: "input-available"