Flowise icon indicating copy to clipboard operation
Flowise copied to clipboard

[BUG] Conversational Retrieval Agent can't connect to Azure Chat open AI.

Open eheading opened this issue 1 year ago • 10 comments

Describe the feature you'd like Conversational Retrieval Agent can only connect to Chat open AI now, it can't connect to Azure Chat open AI. Please consider to support it. Thanks.

eheading avatar Sep 02 '23 07:09 eheading

Is the problem solved?

dzbaiyang avatar Sep 02 '23 16:09 dzbaiyang

Would be eager to see this issue fixed. Need to connect Azure OpenAI LLM.

paulduraiin avatar Sep 03 '23 19:09 paulduraiin

Is the problem solved?

No, the problem is still here. Azure open AI can only do retrieval QA on Flowise and it can't work on conversational retrieval chain. As a result, we can't use memory in chains and it lets Azure open AI not useful enough on Flowise AI. It can only do simple Q&A in such case.

Please correct me if I was wrong. I am still learning it actually. Many thanks.

eheading avatar Sep 04 '23 04:09 eheading

Hi @eheading,

I believe this is not a bug as the agentType: 'openai-functions' do not support Azure OpenAI Tested Below: image

[llm/error] [1:chain:AgentExecutor > 2:llm:ChatOpenAI] [1.28s] LLM run errored with error: "Request failed with status code 404 and body {\"error\":{\"message\":\"Unrecognized request argument supplied: functions\",\"type\":\"invalid_request_error\",\"param\":null,\"code\":null}}"
[chain/error] [1:chain:AgentExecutor] [1.28s] Chain run errored with error: "Request failed with status code 404 and body {\"error\":{\"message\":\"Unrecognized request argument supplied: functions\",\"type\":\"invalid_request_error\",\"param\":null,\"code\":null}}"

cc @HenryHengZJ

chungyau97 avatar Sep 05 '23 11:09 chungyau97

Hi @chungyau97 Yes, I know it's not a bug. That's why I listed it's a feature request originally. Thanks.

eheading avatar Sep 05 '23 12:09 eheading

@HenryHengZJ The retrieval agent works as expected, when changing the model type from ChatOpenAI to BaseModel. I don't think it is a good solution, but it works. See patch at https://github.com/exdatic/flowise/commit/a05dd2b55998a8116430c2294bda1901c6b3322a.

zeitderforschung avatar Sep 29 '23 08:09 zeitderforschung

Facing exactly the same issue: I'm not able to successfully call any service on our endpoint and all calls ends with this error. I did a test and tried to call CURL command from our server where I have deployed Flowise. Both chat and embedding services, when utilized via CURL works. When I setup configuration in Flowise, both calls ends with 404 status code (no body). I've tested all possible configurations (using both types - Agents and Chains)...No success. Any idea when there will be a fix?

Jakub-Zak avatar Jan 30 '24 10:01 Jakub-Zak

I would like this to work as Azure OpenAI is becoming most used more and more. So far, I have failed to make it work. If we ssh to docker, I can reach Azure OpenAI services but not in Flowise.

Proteusiq avatar Feb 15 '24 19:02 Proteusiq

Is the problem solved?

No, the problem is still here. Azure open AI can only do retrieval QA on Flowise and it can't work on conversational retrieval chain. As a result, we can't use memory in chains and it lets Azure open AI not useful enough on Flowise AI. It can only do simple Q&A in such case.

Please correct me if I was wrong. I am still learning it actually. Many thanks.

Could you share QA retrieval example that works?

Proteusiq avatar Feb 21 '24 22:02 Proteusiq

Lots of thanks @dkindlund 🙏🏿🫶🏾. Everything is working perfectly

Proteusiq avatar Feb 26 '24 22:02 Proteusiq