Jared Tracy
Jared Tracy
Are you able to share an entry in the server error log?
Your chat doesn't have a memory node. Add a simple memory node, and you'll see the chat_history value include prior messages.
Do you have screenshots from the prior version where this was working? Or can you rollback and show screenshots of the prior node working as you're expecting it to?
@matrixmayhem Thanks for the additional information. That has helped me identify that the QA chain was working up to at least version 1.4.9.
Are you able to provide some screenshot examples of the difference you're experiencing?
What if you make the same call via the api using postman?
> @YAYJAY you can modify the title color: > > ``` > theme: { > button: { > backgroundColor: "" // } > } > ``` Echoing @HenryHengZJ's prior comment....
@HenryHengZJ This bug fix does not address the issue with Subtitles that is causing initializeNodes to fail. Instead, this solution prevents a single node failing to load in initializeNodes from...
@niztal You could accomplish that using overrideConfig. You'd have crossover issues. For example, what if accidentally place the customer_id 12345 on the website that's supposed to have customerId of 56789?...
@niztal Using the embedded chat, you'd set your variable in the [chatflowConfig](https://github.com/FlowiseAI/FlowiseChatEmbed?tab=readme-ov-file#configuration) < link to docs. You would then use that variable in your flow to adjust your sql query...