Troubleshooting for GitLab Duo with Amazon Q

The following information can help you troubleshoot common issues you might come across for GitLab Duo with Amazon Q.

Why did authentication stop working after I changed the GitLab UUID?

Authentication breaks when you change the GitLab UUID. When you change an GitLab UUID, you need to offboard and then reonboard to Amazon Q with your GitLab instance that has the new GitLab UUID. For more information, see Getting started with GitLab Duo with Amazon Q.

How do I make sure if my IAM role is able to access my GitLab instance?

After providing your IAM role ARN when configuring GitLab Duo with Amazon Q and save the changes, you can confirm that the application is being created in the Amazon CloudWatch console log. For more information, see What is Amazon CloudWatch?.

After the application is created, you can see in the GitLab configuration page that the settings have been saved. In the navigation pane, choose Applications to confirm that the Amazon Q OAuth application is created. You can then add an Amazon Q user that was dynamically created.

Why is a code transformation job paused?

Your code transformation job was paused because the rate of processing transformation jobs in controlled based on demand. Your transformation job is waiting to be processed while another is in progress.