GitLab Duo Chat Error M3003: Unable to Read Merge Requests on GitLab 17.10

 

Description

GitLab Duo Chat allows users to ask questions about specific merge requests to get AI-powered summaries and analysis. Some self-managed customers running GitLab 17.10 have reported encountering error code M3003 when attempting to use Duo Chat functionality related to merge requests. The error message states "I'm sorry, I can't generate a response. You might want to try again. You could also be getting this error because the items you're asking about either don't exist, you don't have access to them, or your session has expired. Error code: M3003". This error occurs when trying to ask Duo Chat questions about specific merge requests, such as requesting summaries or analysis of merge request content.


Impacted offerings:

  • GitLab Self-Managed
     

Impacted versions:

  • GitLab 17.10
     

Prerequisites

Confirm the following:

  • Your self-managed instance is running GitLab version 17.10
  • You have an active GitLab Duo Enterprise subscription
  • Other Duo Chat features (general questions, code explanations) are functioning properly
  • You can reproduce the M3003 error when asking Duo Chat about merge requests
     

Solution

The M3003 error when asking Duo Chat about merge requests on GitLab 17.10 is a known compatibility issue with the GitLab hosted AI Gateway. The only resolution is to upgrade your GitLab instance to version 17.11 or later.

Steps to resolve:

  1. Plan your upgrade to GitLab 17.11 or later following the GitLab upgrade documentation
  2. Perform the upgrade to your self-managed instance
  3. Verify that Duo Chat can now successfully answer questions about merge requests

Note: There is no workaround available for this issue on GitLab 17.10. An upgrade is required to restore full Duo Chat functionality with merge requests.

Cause

This issue occurs due to a compatibility problem between GitLab 17.10 and the GitLab hosted AI Gateway that specifically affects the merge request reader tool functionality. The underlying technical issues include JSON prompt truncation and processing errors in the AI Gateway when handling merge request data from GitLab 17.10 instances. This was resolved in GitLab 17.11 and later versions.

Related Links

 

On this page...