extract from history
# 🤝help
m
Hey there, I wanted to improve my current awsering message system to be more user friendly, The new system checks if the user has a problem, and if the question is already asked so it doesn't ask twice for the awnser. https://cdn.discordapp.com/attachments/1232255188438356029/1232255188673499206/image.png?ex=6628ca93&is=66277913&hm=d2ecf4d7338725a9d44c1d17e0094cace5f42724b0fb225d0f9df27e345bfbb6&
Hey there, I wanted to improve my current awsering message system to be more user friendly, The new system checks if the user has a problem, and if the question is already asked so it doesn't ask twice for the awnser. I wanted to use extract from histoy feature if the user already has asked the question so the user doesnt need to ask twice. In therie it shuold work. How ever, when adding it to the system the following happends. 1. It detects that the user already asked the question, This is good 2. It skips the step where it asks the user for the question, This is good 3. It comes to the raw imput, where i have set extract from history to 1, it detects the message correctly according to the logs, But, skips awnsering the question and goes to the next card. Now, in step 3 it skips the awnsering part. There are 0 errors in the logs, it shows that it extracted the message successfully. how ever, thats it. 0 logs about awnsering the question. and in the chat also 0 awnsers. It just goes to the nest step. So i was wondering how i can solve this. My old system saved the question in a variable, and used the knowledge agent to save the awnser in the variable, That variable was pasted in a text card. Problem is that if it could not find the awnser, it would just output: @workflow.awnser. That's why i want to switch to raw imput. Because its way more powerful in finding answers in the knowledge base and it it fails you can set it to try it again so it almost always has a message. I hope i explained everthing good, my english isn't the best. Here is a screenshot of how i made the workflow that doesn't work.
3 Views