Skip to main content

Known Issues

General​

  • Online status of Razer AI

    The Online status of Razer AI service appears green when it is installed on another machine.

  • FPS inaccuracy

    In some cases when the game is displayed on a secondary monitor, FPS detected is inaccurate.

  • Screen video capture with AMD graphics cards

    The screen recording feature in Razer QA Co-AI is currently incompatible with PCs using AMD graphics cards. Our team is actively working on resolving this issue.

  • Video not saved at session end

    If a video is recorded just before a report is finalized, it may not upload correctly due to a timing conflict. We recommend finishing video captures a few moments before ending the session to avoid this issue.

  • Live updates to service.conf affect health checks

    Modifying the configuration file while the AI Service is running can disrupt health monitoring. To restore accurate health status, please restart the service after making changes.

  • Visual Issue: FPS Displayed as 0

    In some cases, the FPS may incorrectly show as 0. This is a known issue caused by an external library. If you encounter this problem, please contact support for assistance.

  • Update banner not disappearing

    The “Update available” banner in the web app will remain visible until a new report is created using the latest version of the AI Service.

  • Performance metrics sampling

    Currently, performance metrics are sampled exclusively on the host PC. Support for remote or distributed sampling is not yet available

Rare Issues​

  • Video saving failure

    In rare instances, video files may fail to save due to internal encoding or timing errors. We are investigating this issue to improve reliability.

  • Installer blocked during update

    During service updates, Windows may lock certain files, preventing the installer from completing successfully. If this occurs, uninstalling the application and reinstalling it manually can resolve the issue.

  • Razer Chroma SDK initialization failure

    Using an outdated version of the Razer Chroma SDK may cause initialization to fail. Reinstalling the latest version resolves this issue.

  • Jira workspace assignation

    Currently, it's not possible to disconnect Jira from Razer QA Co-AI's General Settings—this functionality will be available soon. Additionally, if a user has connected their Jira account to multiple workspaces and then revokes Razer QA Co-AI's access from their Jira settings, attempting to reconnect to a different workspace may result in the Jira API returning the incorrect target workspace in some cases.