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

Final update

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.

1. Resolved · Nov 3, 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.
2. Identified · Nov 3, 13:24 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.
3. Investigating · Nov 3, 12:24 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.