GitLab: Elevated errors in background job processing
Affected components: Background Processing
Timeline of updates
- identified
We've identified a recent code change as the likely cause of elevated Sidekiq job execution errors on the low-urgency-cpu-bound shard, which may delay processing of some background jobs. Mitigations are in progress. We'll continue to update as soon as the mitigation is merged and deployed.
- resolved
A recent code change was rolled back and the error rates have subsided since it was merged. Our team has been monitoring and performance has returned to expected levels. This incident is now resolved. https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22335 (opens in new tab)
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
77b56ef6711102fe…
Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitLab, started 2026-06-18 14:02 UTC, resolved after 2.8 h, 2 update(s).
- Title
- Elevated errors in background job processing
- Vendor
- GitLab
- Date
- URL
- https://rewindex.com/company/gitlab/incidents/6a33fa8ef7a0500610c184bd
GitLab profileRecent GitLab incidentsAll outages on June 18, 2026GitLab in June 2026MarkdownJSON