Companies / GitLab / incidents

GitLab: Flows failing with In Memory Error

Affected components: GitLab Duo

Timeline of updates

1. identified2026-03-03 09:01 UTC

   We've identified failures for remote flows, including Duo Developer, and other foundational workflows. Users are seeing failures such as "Session failed" when requesting code reviews through GitLab Duo. The root cause has been identified and a revert is ongoing. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429

2. identified2026-03-03 09:31 UTC

   No material updates at this time, the revert is still in progress. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429

3. identified2026-03-03 10:01 UTC

   Still no material updates at this time, the revert is in progress. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429

4. identified2026-03-03 10:46 UTC

   Still no material updates at this time, the revert is in progress. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429

5. monitoring2026-03-03 11:03 UTC

   The revert has been merged, and the flows are now operational. We are now monitoring the situation. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429

6. resolved2026-03-03 11:46 UTC

   This incident is now resolved. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429

Rewindex changes for this incident

• Major incident: Flows failing with In Memory Error 2026-03-03 09:01 UTC

Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab). GitLab profile · Recent GitLab incidents · Markdown · JSON