https://discord.gg/botpress logo
Join Discord
Powered by
Conversations in botpress
# 🤝help
s
New conversations tab is much less useful, having the inability to scroll and see conversations on the fly. There is nothing showing up on the summary in conversations also. And when I do click to view a conversation I just get 'Something went wrong. Please try again later' so it's also not working as expected.
b
what we found is that people wanted more detail on conversations and actually that reading them on the fly wasn't providing too much value
but can you show me an example of the error you're running into?
& equally - it's possible that summaries are only passed in for net new conversations since the feature was started to be rolled out this morning
s
Small example here. Sometimes the conversation is showing when I click, but over half the time this is what i see when i click 'view in conversations'
Yeah had a look again, majority of conversations i cant see
Why I found the previous one very benefitial is because I have high enough traffic volume. So can have up to 400 people using the system over a 24 hour period, and sometimes many people at once. Being able to quickly see the conversations allows me to monitor for any bugs that pop up, and then I can act fast to solve them. Having to click through adds an extra step and makes it difficult to monitor with high volumes in a user friendly way.
All my conversations have been of the last 2-3 hours, but don't have summary populated for any of them
b
bugs popping up should be showing in the 'Issues' tab, but I understand your workflow better
what kinds of bugs can you ascertain from a conversation that isn't coming from Issues?
s
I guess it would be two types of bugs. Ones are connected to something external which might do something unexpected and return a wrong answer (e.g. a stack AI call that answers incorrect information from a knowledge base). Nothing is broken, but we might want to tweak a prompt or the knowledge base there. For an example that might not be an "Issue" inside botpress but something we want to monitor could be say an AI Generate which is used as a classifier, but it missclassifies because the prompt could be better or needs to be tweaked. Because of this the user goes down a wrong route. Nothing actually broke, more so my prompt didn't work as expected
b
the thing is we don't consider these bugs on the Botpress side, but I see what you're saying
an easier way to manage this, in my opinion, would be to save the responses generated by stackAI to a table for periodical review after
s
Yep fair, about the call on the stackAI side not being seen as a bug for botpress. We do store data and responses, it's just important to have live monitoring, as we kind of know when traffic will hit and we can watch conversations. Do periodic reviews also to catch other issues.
PreviousNext
Powered by