openclaw - 💡(How to fix) Fix [Bug]: Regression: tool-execution replies intermittently not delivered in webchat on 2026.3.22+ (works on 2026.3.13) [1 participants]

Fix Plan

To address the intermittent missing final reply issue in tool-result flows after upgrading to 2026.3.22 or 2026.3.23-2, we will modify the reply-payloads-dedupe and shouldSuppressMessagingToolReplies functions to ensure legitimate tool-result payloads are not suppressed or deduped.

Step-by-Step Solution:

1. Review and adjust reply-payloads-dedupe:

   • Inspect the reply-payloads-dedupe function to identify the logic that might be causing the suppression of legitimate tool-result payloads.
   • Adjust the function to exclude tool-result payloads from deduplication based on specific identifiers or flags.

2. Modify shouldSuppressMessagingToolReplies:

   • Examine the shouldSuppressMessagingToolReplies function to understand under what conditions it suppresses messaging tool replies.
   • Update the function to not suppress replies for tool-result flows, potentially by adding a conditional check for the type of reply or the context in which it's being sent.

3. Update route-reply/dispatch path:

   • Review the changes made to the route-reply/dispatch path in the 3.22+ versions.
   • Ensure that the updated path correctly handles tool-result payloads and does not inadvertently drop or suppress them.

Example Code Adjustments:

// Example adjustment to reply-payloads-dedupe
function replyPayloadsDedupe(payloads) {
  // Filter out tool-result payloads from deduplication
  return payloads.filter(payload =>!payload.isToolResult);
}

// Example adjustment to shouldSuppressMessagingToolReplies
function shouldSuppressMessagingToolReplies(reply) {
  // Do not suppress tool-result replies
  if (reply.type === 'toolResult') {
    return false;
  }
  // Existing suppression logic here
}

// Ensure route-reply/dispatch path correctly handles tool-result payloads
// This might involve updating routing conditions or adding specific handling for tool-result types

Verification

To verify that the fix worked:

• Deploy the updated code to the production environment.
• Perform the steps to reproduce the issue as described.
• Monitor the behavior of tool-result flows in webchat to ensure that final replies are consistently delivered.
• Test with various tool-heavy tasks to confirm the reliability of result delivery across different scenarios.

Extra Tips

• Regularly review and test changes to message handling and dispatch logic to prevent similar issues.
• Consider implementing logging or monitoring to detect and alert on potential reply suppression or deduplication issues in the future.
• Ensure that any updates to the reply-payloads-dedupe and shouldSuppressMessagingToolReplies functions are thoroughly tested to avoid unintended side effects on other types of messages or workflows.