简单内存节点常见问题

¥Simple Memory node common issues

以下是 简单内存节点 的一些常见错误和问题，以及解决或故障排除步骤。

¥Here are some common errors and issues with the Simple Memory node and steps to resolve or troubleshoot them.

单内存实例

¥Single memory instance

如果你向工作流中添加多个“简单内存”节点，则默认情况下所有节点都访问同一个内存实例。执行会覆盖现有内存内容的破坏性操作时务必谨慎，例如在 聊天内存管理器 节点中执行“覆盖所有消息”操作。如果你需要在工作流中使用多个内存实例，请在不同的内存节点中设置不同的会话 ID。

¥If you add more than one Simple Memory node to your workflow, all nodes access the same memory instance by default. Be careful when doing destructive actions that override existing memory contents, such as the override all messages operation in the Chat Memory Manager node. If you want more than one memory instance in your workflow, set different session IDs in different memory nodes.

管理会话 ID

¥Managing the Session ID

在大多数情况下，sessionId 会自动从“聊天消息触发”中获取。但你可能会遇到包含短语 No sessionId 的错误。

¥In most cases, the sessionId is automatically retrieved from the On Chat Message trigger. But you may run into an error with the phrase No sessionId.

如果你遇到此错误，请先检查聊天触发器的输出，确保其中包含 sessionId。

¥If you have this error, first check the output of your Chat trigger to ensure it includes a sessionId.

如果你未使用“聊天消息触发”功能，则需要手动管理会话。

¥If you're not using the On Chat Message trigger, you'll need to manage sessions manually.

出于测试目的，你可以使用静态键，例如 my_test_session。如果你使用此方法，请务必在激活工作流之前设置正确的会话管理，以避免在生产环境中出现潜在问题。

¥For testing purposes, you can use a static key like my_test_session. If you use this approach, be sure to set up proper session management before activating the workflow to avoid potential issues in a live environment.