[Bug]: `bad escape \P at position 374 (line 18, column 23)` when using the graph feature

[Randname666]

Is there an existing issue for the same bug?

• [X] I have checked the existing issues.

Branch name

main

Commit ID

c943517

Other environment information

Hardware: VMWare Workstation 16.2.3, Intel Xeon X5690 (6 threads assigned), 24GB RAM assigned, No available GPU
OS Type: Ubuntu Server 24.04 LTS

Actual behavior

Flow of the graph crashed at node retrieval-windows and responds error bad escape \P at position 374 (line 18, column 23) after a Retrieval node. The graph is shown in the picture: Node retrieval-windows has following settings:

(other categories are omitted as those categories and related nodes are running fine.)

Name: Windows
Description: 问题中包含Windows字样或一个Windows版本。
Examples:
Windows
Windows Server
Windows 11
Windows 10
Windows 7
Windows Vista
Windows XP
XP系统
To: retrieval-windows

The generate node LovelyTipsCall is using qwen-plus model.

There is no meaningful information given in the log.

I'm really sorry, but the document to be used to generate the knowledge database for this graph, and probably the sliced content is not allowed to be distributed according to its copyright claims.

Expected behavior

Flow of the graph continues to run and reply the final result in the chat window.

Steps to reproduce

Build a similar graph and run.

Additional information

This is probably caused by some kind of strange characters in either the source document or sliced results ?