ROVO throws exception when the conversation history becomes too large to be stored.

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • Component/s: Agents
    • None
    • Severity 3 - Minor

      Issue Summary

      Sometimes, the response is too big to be stored in history at backend. This caused exception in ROVO's responses as well. 

      In front end we may see :  ROVO agent error - Internal Server error 500

      Steps to Reproduce

      N/A

      Expected Results

      It should always generate a response within the limit it supports.

      Actual Results

      In front end we may see :  ROVO agent error - Internal Server error 500

      Workaround

      n/a

            Assignee:
            Thanh Tran
            Reporter:
            Harsaranjeet Kaur
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: