[Bug]: Agent flow requires two completions of the conversation after creating a session if there are input parameters.

[stardyun]

Is there an existing issue for the same bug?

• I have checked the existing issues.

RAGFlow workspace code commit ID

409310a

RAGFlow image version

v0.16.0-139-g58a8f1f1 full

Other environment information

Actual behavior

Repeated messages

Expected behavior

After “Create session with agent”, call “Converse with agent” and get an answer immediately.

Steps to reproduce

01. Create session with agent(the Begin component in your agent takes required file parameters)
02. Converse with agent (Need to ask questions twice.)
03. List agent sessions (There are 2 duplicate messages.)

Additional information

1. Create session
   

2. Converse with agent
   

3. Converse with agent again
   

4. View message history
   

[KevinHuSh]

Agent always talks firstly.

[stardyun]

Agent always talks firstly.

However, it takes two rounds of dialogue requests to get a response, and the message records are also repeated for two rounds.

[vifun]

it takes two rounds of dialogue requests to get a response, and the message records are also repeated for two rounds.
I have also encountered the same problem.

[KevinHuSh]

The first round is to get the session ID which will be applied for the successive conversations.

[vifun]

After obtaining the session ID through the use of the interface/api/v1/agents/{agent_id}/sessions, the first question-answer interaction is conducted using the interface/api/v1/agents/{agent_id}/completions, and the result is normal. When using the previous session ID to ask the second question, at this time, the following data will be returned: {
"code": 0,
"data": true
}, and it will only respond normally after you make another request.

[vifun]

[vifun]

Does the session ID have an expiration time?

[KevinHuSh]

It may be related to your entire flow. Is it normal via UI?

[vifun]

The UI is also not functioning properly.

[vifun]

[KevinHuSh]

[vifun]

Thank you! If I want to output the SQL statements generated by LLM into the dialog box, how can I do it? Or is there an interface to access the running results of the nodes?

[KevinHuSh]

ExecSQL will adjust the SQL if fail. So, the real SQL can't be obtained.

[vifun]

In the future plan, is there a feature that enables LLM to generate SQL statements, and then ExecSQL can execute these SQL statements and output the results to the dialog box?