Issues with Slack Message References in Project Updates

Hey guys, any idea why the slack messages referenced by dust as source for generating the answer often points to messages that don’t really seem relevant at all? The answer would say for instance “Project will be delivered on march 31st [1]” and when I check the [1] reference it’s a message that is definitely not the source of that info (but the channel itself might be)

👀1

3 comments

Thibault
·
·
Hi Simon Corompt, on Slack, this is likely the result of how retrieval happens on Dust. Essentially: we group messages together in 'chunks', and then get the most relevant chunks for the query.
if the message is in a thread, then the thread will be its own 'chunk' of text and the reference will be correct.
if the message is not in a thread, it's likely to be grouped with other messages. The citation therefore links towards one of the messages from the group, but not that specific one.
It's a known friction and we will likely improve it in the future. The good news is that the citation still corresponds to a piece of text that was relevant. hope this helps
Simon Corompt
·
·
Super clear thanks! Are chunks created by date? Meaning even if the citation doesn’t point to the exact message, I can be sure that the relevant data is somewhere close to that message if I want to find it?
Thibault
·
·
they are grouped based on order of appearance, so you could expect that the cited chunk is not too far from the real source
🙏1