Why is the chat history missing in old workflow executions?

Below is some guidance on restoring chat functionality and understanding the plain markdown output in your old execution:

Why the Chat Button and History Are Missing

Older executions may not include the metadata or session data required for the chat interface. In particular, if the workflow wasn’t configured to load previous sessions (for example, by connecting a memory sub-node), then the chat UI won’t have the extra context needed to display the chat button or format the output as chat messages. Instead, you’ll see plain markdown text when inspecting node outputs.

What’s Needed for Proper Chat UI Rendering

For new executions, ensure that:

1. Load Previous Session is configured (set to “From Memory” if needed).
2. Both the Chat Trigger node and your Agent (or Chain) node are connected to the same memory sub-node.
   • In the memory node, set the Session ID to “Take from previous node automatically” unless you have a custom setup.
3. The incoming data uses the appropriate keys (such as text or output) so that the Chat Trigger node knows which field to display as the chat response.

How to Proceed with Old Executions

Unfortunately, old executions won’t be updated retroactively with these enhancements. This means:

• Plain Markdown Output: The old executions only stored the raw markdown (or plain text) output, so it won’t automatically display as formatted chat history.
• Missing Chat Button: Since the UI relies on session metadata to display the chat interface, executions from before the correct session configuration will not show the Chat button.

Recommended Steps

1. Update and Re-run Your Workflow:
   Make sure your current Chat Trigger node is configured with the proper session loading and memory connections. New executions should then show the chat button and formatted output.

2. Verify Node Configuration:

   • For the Chat Trigger, set Load Previous Session to “From Memory” if you want to retrieve previous messages.
   • Ensure you attach the same memory node to both the Chat Trigger and Agent nodes.

3. Accept Limitations for Old Executions:
   Since the improvements in chat message formatting and session handling were introduced after those executions, you can only see raw markdown in past runs. Re-running the workflow with the updated configuration will restore the full chat functionality.

Following these steps should help you restore the output formatting and chat interaction for future executions. Unfortunately, past executions won’t display the enhanced view since they lack the additional metadata needed by the chat UI.