Custom Assistant Knowledge (Document Stores) dropdown still not working in 3.1.1

[Mhydrosmart]

Describe the bug

Custom Assistant cannot attach an existing synced Document Store under Knowledge (Document Stores).

Version
Flowise 3.1.1

Environment
Windows 10. Firefox. Hosted on Render

To Reproduce

1. Create a Document Store.
2. Add a JSON file via JSON File loader.
3. Configure loader/splitter and process until the store shows green sync.
4. Go to Assistants > Custom Assistant.
5. Try to select the Document Store under Knowledge (Document Stores).

Expected behavior
The existing Document Store should appear and be selectable.

Actual behavior
The dropdown does not work / does not populate / does not allow selection.

What I tried

• Reloaded the page
• Logged out and back in
• Created a brand-new Custom Assistant
• Updated Flowise from 3.1.0 to 3.1.1
• Confirmed the Document Store shows green sync

Result
Still broken on 3.1.1.

Related issue
Possibly related to closed issue #3710:
[BUG] Flowsie 2.2.2 does not show Knowledge (Document Stores) in dropdown for Custom Assistants

To Reproduce

1. Create a Document Store.
2. Add a JSON file via JSON File loader.
3. Configure loader/splitter and process until the store shows green sync.
4. Go to Assistants > Custom Assistant.
5. Try to select the Document Store under Knowledge (Document Stores).

Expected behavior

Expected to be able to select an upserted Document store

Screenshots

No response

Flow

No response

Use Method

None

Flowise Version

3,1,1

Operating System

Windows

Browser

Firefox

Additional context

Possibly related to closed issue #3710:
[BUG] Flowsie 2.2.2 does not show Knowledge (Document Stores) in dropdown for Custom Assistants

[prd-hoang-doan]

@Mhydrosmart In order to use document store in the model/assistant, you have to create a document store -> add loader -> status SYNC -> Upsert Chunks -> status UPSERTED.
So, you can move to the next step to finish this.

[Mhydrosmart]

@prd-hoang-doan Thanks for this. I realised that this afternoon too, and I successfully got to UPSERTED. I was then able to select the document store in the custom assistant. I located it on my Render disk. (/opt/render/.flowise) It is just one modest JSON correctly chunked. However, even if I just send 'hi' to it in the custom assistant, I just get request time out after 2 mins...

[prd-hoang-doan]

@Mhydrosmart Thank you for providing your detailed issue. Could you try it without Knowledge (Document Store)?
If the response is successful, the LLM connection is good. I suspect there is an issue related to the Vector DB connection here.
The function still works well under local development.

[Mhydrosmart]

@prd-hoang-doan Thanks, I tried it with no document store. Still a long timeout. I turned off streaming and it times out with a different error message (attached). I also tried gpt4.1, and 4.1 nano with the same result.

[Mhydrosmart]

@prd-hoang-doan - update. I removed a timeout value and it told me '400 Unsupported parameter: 'top_p' is not supported with this model.' I remove the Top P value (which I had put at 1) and it works!

[HenryHengZJ]

actually, we are planning to turn the whole custom assistant to using Agent node from agentflow v2. Currently its using ToolAgent from chatflow behind the scene

[HenryHengZJ]

and thanks @prd-hoang-doan for helping out!

[Mhydrosmart]

Thanks again @prd-hoang-doan . That sounds good @HenryHengZJ - I intend to explore agentflow v2 time permitting, but for now having an easy route to replace OpenAI AI assistant (deprecating in August) with Custom Assistant is very useful.

[mittayrmalak-boop]

Thanks for testing that and sharing the details.

…

On Tue, Mar 31, 2026, 3:00 AM Mhydrosmart ***@***.***> wrote: *Mhydrosmart* left a comment (FlowiseAI/Flowise#6064) <#6064 (comment)> Thanks again @prd-hoang-doan <https://github.com/prd-hoang-doan> . That sounds good @HenryHengZJ <https://github.com/HenryHengZJ> - I intend to explore agentflow v2 time permitting, but for now having an easy route to replace OpenAI AI assistant (deprecating in August) with Custom Assistant is very useful. — Reply to this email directly, view it on GitHub <#6064?email_source=notifications&email_token=CAXJWKUKTE3O3VGSRA622I34TN3KFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGA3DOOJUHE22M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4160679495>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CAXJWKU3SMVOTPT3KUIAGYL4TN3KFAVCNFSM6AAAAACXAB5JYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRQGY3TSNBZGU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>