Troubleshooting the GitLab Duo Agent Platform

  • Tier: Premium, Ultimate
  • Add-on: GitLab Duo Core, Pro, or Enterprise
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

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:

  1. Ensure you have at least Developer role in the project.
  2. Ensure GitLab Duo is turned on and flows are allowed to execute.
  3. Ensure the required feature flags are enabled for the flow you're trying to use. For the latest flag information, check the documentation history for the feature.
  4. If it still does not work:
    1. Disable the affected flow in the top-level group and save the configuration.
    2. Enable the affected flow in the top-level group and save the configuration.
    3. Wait a few minutes for the setting to propagate across your groups.

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 branches with the workloads/ prefix (for example, workloads/a1b2c3d4e5f).

To configure push rules for a project:

  1. Find the email address associated with the service account:

    1. In the upper-right corner, select Admin.
    2. Select Overview > Users and search for duo-developer.
    3. Locate the duo-developer user and copy the email address.

  2. Allow the email address to push to the project:

    1. On the top bar, select Search or go to and find your project.
    2. Select Settings > Repository.
    3. Expand Push rules.
    4. In Commit author's email, add a regular expression that allows the email address you just copied.
    5. Select Save push rules.

  3. Allow the workloads/ and duo/feature/ branch prefixes:

    1. In the Push rules section, find Branch name.
    2. Add a regular expression that allows branches starting with workloads/ and duo/feature/. For example: ^(workloads|duo/feature)/.*$
    3. Select Save push rules.

If you are an administrator, you can create push rules for the instance:

  1. In the upper-right corner, select Admin.
  2. Select Push rules.
  3. Follow the previous steps to allow Commit author's email and Branch name.
  4. Select Save push rules.