Expired GitLab project access tokens not refreshing causing failures in posting commit statuses

Update timeline

1. investigating Nov 03, 2026, 12:24 PM UTC

   We’re investigating an issue with the GitLab integration that is causing CI job commit statuses to not post back to GitLab. This is limited to existing projects with a GitLab integration whose project access token has expired and was not refreshed. It is impacting a small number of customers on the EU2 (Azure) region anytime after 06:00 UTC (01:00 AM Eastern) on 3 November. Affected customers may see missing pipeline statuses on merge requests, which can block merges that require passing statuses. New project configurations and new GitLab integrations are not impacted. There is currently no known workaround for affected existing projects, and reconnecting the repository does not resolve it. Our engineers are working on a resolution and we will provide updates approximately every 30 minutes, or as soon as new information becomes available. Please contact Support at [email protected]: mailto:[email protected] if you believe you are affected.

2. identified Nov 03, 2026, 01:24 PM UTC

   We have identified an issue with Gitlab project access tokens not being refreshed. Our engineers are working on a fix for this, and we will provide an update shortly.