# dbt Cloud: Expired GitLab project access tokens not refreshing causing failures in posting commit statuses

> dbt Cloud did not post CI job commit statuses back to GitLab. The problem affected existing projects in the EU2 (Azure) region with an expired GitLab project access token. dbt Cloud reports that the issue is resolved. The outage lasted 1 hour and 51 minutes.

- Provider: [dbt Cloud](https://outages.cc/dbt.md)
- Type: Incident
- State: Resolved
- Worst impact: Degraded performance
- Started: 2026-11-03 12:24 UTC
- Resolved: 2026-11-03 14:15 UTC (lasted 1 h 51 min)
- Official update: https://status.getdbt.com

## Updates from dbt Cloud

### resolved, 2026-11-03 14:15 UTC

The issue has been resolved, and all affected systems are now functioning normally . Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.

### identified, 2026-11-03 13:27 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.

### investigating, 2026-11-03 12:30 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 [support@getdbt.com](mailto:support@getdbt.com) if you believe you are affected.

### investigating, 2026-11-03 12:27 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 [support@getdbt.com](mailto:support@getdbt.com) if you believe you are affected.