Troubleshooting the GitLab Duo Agent Platform
If you are working with the GitLab Duo Agent Platform, you might encounter the following issues.
View logs
After a flow is created, you can view the flow’s session by going to Automate > Sessions.
The Details tab shows a link to the CI/CD job logs. These logs can contain troubleshooting information.
Flows not visible in the UI
If you are trying to run a flow but it’s not visible in the GitLab UI:
-
Ensure you have at least Developer role in the project.
-
Ensure GitLab Duo is turned on and flows are allowed to execute.
-
Ensure the group you are in has been given permission to use flows.
-
If the top-level group is configured correctly but flows are not visible for an individual project:
- Go to the project.
- Select Automate > Flows.
- In the upper-right corner, select Enable flow from group.
- Select a flow, then select Enable.
-
If it still does not work:
- Disable the affected flow in the top-level group and save the configuration.
- Enable the affected flow in the top-level group and save the configuration.
- Wait a few minutes for the setting to propagate across your groups.
Insufficient permissions to create a new pipeline for imported projects
If you are trying to run foundational flows in an imported project or a project created from a template,
you might get the error: Error in creating workload: Insufficient permissions to create a new pipeline.
To fix this issue:
- Go to the top-level group.
- Select Settings > General.
- Expand GitLab Duo features.
- Under Flow execution, identify the foundational flows you want to turn on.
- Disable the flows in the top-level group and save the configuration.
- Enable the same flows in the top-level group and save the configuration.
- Wait a few minutes for the setting to propagate across projects in the group.
Session is stuck in created state
If a session for your flow does not start:
- Ensure push rules are configured.
Configure push rules to allow a service account
In the GitLab UI, foundational flows use a service account that:
- Creates commits with its own email address.
- Creates a workload pipeline.
Prerequisites:
- Administrator access.
To configure push rules for a project:
-
Find the email address associated with the service account:
- In the upper-right corner, select Admin.
- Select Overview > Users and search for the account associated with the flow.
The account follows the pattern
duo-[flow-name]-[top-level-group-name]. - Locate the service account user and copy the email address.
-
Allow the email address to push to the project:
- In the top bar, select Search or go to and find your project.
- Select Settings > Repository.
- Expand Push rules.
- In Commit author’s email, add a regular expression that allows the email address you just copied.
- Select Save push rules.
-
Allow the
duo/feature/branch prefix:- In the Push rules section, find Branch name.
- Add a regular expression that allows branches starting with ^duo/(fix|feature|refactor|docs/).*
For example:
^(duo/feature)/.*$ - Select Save push rules.
To create push rules for the instance:
- In the upper-right corner, select Admin.
- Select Push rules.
- Follow the previous steps to allow Commit author’s email and Branch name.
- Select Save push rules.