Aura Bot changelog
Changelog of Aura Bot component for Radiohead Aura Platform release
Added
2025-06-19 - TV Content Get Info dialog configuration for channels MP and MH
- Configuration has been added for channels movistar-plus and movistar-home to enable TV Content Get Info use case, now supporting
intent.tv.content_get_info, which allows retrieving detailed information about a specific TV channel. - Related documents:
2025-06-12 - TV None and None dialog configuration for channels MP and MH
- Configuration has been added for channels movistar-plus and movistar-home to enable both TV None and None use cases. Now, user requests that do not make sense in the video domain will trigger the
intent.tv.noneuse case, while the rest will trigger theintent.noneuse case. - Related documents:
2025-06-10 - Negative sound added to actions for channel MH
- Configuration has been added for the channel movistar-home to enable negative sound when requests to Aura Complex Logic Framework (CLF) return error or no content.
- Related documents:
2025-06-09 - New suggestions dialog for channelData V3
- Added new suggestions dialog v3 (/docs/components/global-use-cases/miscellaneous-dialogs/suggestions-dialog-v3/) so that it can be activated when needed in the normalized use cases.
2025-06-09 - New aura-bot environment variable
- New environment variable is added to aura-bot to handle the number of suggestions to be shown in use cases.
- Related documents:
2025-06-09 - Add smalltalk v3 use cases for channel MH and MP in Spain OB
- The normalized smalltalk use cases adapted to Aura request-response v3 model, have been activated for the channel movistar-plus (MP) and movistar-home (MH) in Spain OB.
2025-06-09 - Add init v3 use cases for channel MP in Spain OB
- The normalized use case init adapted to Aura request-response v3 model, has been activated for the channel movistar-plus (MP) in Spain OB.
Changed
2025-07-03 - Improved MongoDB server connection settings
- The complete set of environment variables for MongoDB connection has been added to the aura-bot component. This includes settings for maximum and minimum pool sizes, idle time, retry writes and reads, heartbeat frequency, server selection timeout, socket timeout, connection timeout, and read preference.
- Related documents:
Fixed
2025-06-23 - Error message after bypass timeout
Resolved a bug in the Aura Conversational experience on STB (Brazil, ES) where, after a bypass timeout period (240 seconds) during a Custom Recommendation dialog, the subsequent user messages (e.g., greetings) triggered a generic error response instead of the appropriate intent-based reply. After this bypass timeout, the system incorrectly attempted to access the topIntent property from an undefined object, resulting in an unhandled exception in the tv-custom-recommendation dialog flow.
This has been fixed through an improved session management logic to correctly handle post-timeout interactions. If a session has expired, the bot now properly reinitializes context and safely processes the next user message (e.g., COMMON.GREETINGS) instead of throwing an internal error.
2025-06-17 - Fixed metrics to be aggregated by path in Prometheus metrics
- For certain aura-bot metrics, there was a wrong result when aggregating them by path to Prometheus metrics. Now, new paths for
home-devices-management/v2endpoints have been created.