Error: enter idle | Error Details: | Error Code:14

Hi Team,

Speak to the character in Unreal Engine, I get this error message on the chat widget, checking the output log, this is the message highlighted

ConvaiGRPCLog: Warning: OnStreamFinish: Status.ok():Not Ok | Debug Log: | Error message:enter idle | Error Details: | Error Code:14 | Character ID:60e087de-76af-11ef-80ce-42010a7be011 | Session ID:951063b9b8b45373a01db585e7642a32
ConvaiChatbotComponentLog: Warning: UConvaiChatbotComponent Get Response Failed! | Character ID : 60e087de-76af-11ef-80ce-42010a7be011 | Session ID : 951063b9b8b45373a01db585e7642a32

This is what ChatGPT has to say about this error message:

The error appears to be related to the gRPC communication within the Convai system, where error code 14 typically indicates an “Unavailable” status. In essence, the system is experiencing issues in establishing or maintaining a stable connection, leading the component to enter an idle state. Below is a step-by-step troubleshooting guide:

  1. Network Connectivity and Service Availability:
    Verify that the network connection is stable and that the Convai service endpoint is accessible. A transient network disruption or maintenance downtime can trigger such errors.

  2. Endpoint Configuration and Firewall Settings:
    Ensure that the gRPC endpoints are correctly configured in your application. Review firewall settings and any proxy configurations that might be blocking or throttling the connection to the service.

  3. Authentication and Credentials:
    Confirm that the authentication tokens or credentials used for accessing the Convai service are valid and have not expired. Misconfigured or outdated credentials may result in failed requests.

  4. Resource Utilization and Load:
    Investigate whether the service is experiencing high load or resource constraints. If the service is under heavy demand, consider implementing retries with exponential backoff as a temporary mitigation strategy.

  5. Error Handling and Logging:
    Enhance your error logging to capture more detailed information surrounding the failure. This additional context can help in isolating whether the issue is intermittent or systemic.

  6. Consulting Documentation and Support:
    Review the Convai developer documentation for any specific notes regarding error code 14 and the “enter idle” message. If the issue persists after the initial troubleshooting steps, it may be necessary to contact Convai support with detailed logs (including the Character ID and Session ID) for further analysis.

By approaching the problem systematically—beginning with network checks and progressing through configuration, authentication, and load assessments—you can methodically isolate and address the underlying issue. This structured troubleshooting approach aligns with both academic research methodologies and practical industry best practices.

Can you please help with this issue? Thanks

Hello @Jeasy_Sehgal,

This is a known issue, and it will be resolved in the upcoming update.

Thank you for your patience!