I’m noticing two display issues when using the Google Search action:
– The search results are not displayed in a smooth scrolling fashion, but instead create a LOT of extra screen movement and flicker as they appear. (For example, when displaying a set of four YouTube videos on a certain topic.)
– The results are formatted nicely (for example, a brief summary of each video with a clickable YouTube image below each, etc.), but then, it adds an unhelpful and confusing duplicate list below that. The duplicate list, in this example, shows the URL and below each the words, “No description found.” The duplicate list serves no function that I can see and makes the output seem confusing and unprofessional.
That second issue is just a feature we added. All hyperlinks are richly displayed as link previews. We have been thinking about turning it off as many users don’t like it. But it’s a tradeoff because many users do want rich previews of hyplerinks!
Perhaps a good solution would be to provide an option for including or not including the secondary listing. In my use case, I instruct the bot to display a menu of options at the end of each output. So when the user chooses an option that displays a list of videos from a Google Search, the menu gets sandwiched between the initial list of videos and the secondary “rich” set of video details.
We have made a change to the system. Now the outputs will not render previews of links. While nice, it seems this was causing issues.
1 Like
@admin_mike Thanks very much, Mike! That resolves the very annoying flickering issue while rendering…YouTube links come back with the thumbnail image of the actual video, so I for one won’t miss the additional “preview”.
Yes, we have not turned off rich previews for youtube videos. Youtube links still display their rich previews so that end-users may watch them within a chat.
My usecase relied on having rich preview. Can we have a toggle for people who want to keep it or off? Please?
Im getting tons of 406 links at the end of output still.
Honestly, this transistion has been a real pain and it is now costing me both time and money, as clients can either:
a. use the old function embed, but not be able to see any chat history or
b. Use the new embed with numerous bugs.
EDIT: Could this be related to the FAB embed? It seems to have a lot of isuues that weren’t there before the migration?
