Time to Bail · Boarding pass
Act. You can stay.
Both values are removed in GitLab 20.0, planned for May 20, 2027. List the new failure reasons instead.[1]
Act means: change a setting or plan before the date. You can stay.
GitLab 20.0 removes old retry:when failure reasons (May 20, 2027)
GitLab 19.0 split two failure reasons into more exact ones. The old names are stuck_or_timeout_failure and job_execution_timeout. You can still use them in retry:when, but you get a warning. GitLab plans to remove them in GitLab 20.0, on May 20, 2027.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
Tick steps as you go. Your progress stays in this browser.
Look for the two old names in .gitlab-ci.yml and in files it includes.
List the new names you need, like no_updates_running or server_timeout_running.
Open the pipeline editor. The warning should be gone.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| GitLab 20.0 release (planned) | May 20, 2027[2] |
|---|---|
| Removed in | GitLab 20.0[1] |
| Deprecated values | stuck_or_timeout_failure and job_execution_timeout[1] |
| Split into new reasons in | GitLab 19.0[1] |
| Until then | They work as aliases for the new reasons, and CI lint shows a warning[1] |
| Replace stuck_or_timeout_failure with | The ones you need of stuck_pending_with_matching_runners, stuck_pending_no_matching_runners, no_updates_running and no_updates_canceling[1] |
| Replace job_execution_timeout with | server_timeout_running and/or server_timeout_canceling[1] |
| GitLab.com | Deprecated features can be removed at any time in the month before the release[1] |
| Pipelines that list the old values | Must use the new values before GitLab 20.0[1] |
Check it yourself. Every fact above links here.
Time to bail on GitLab CI jobs that retry on the old timeout reasons? Act. You can stay. Both values are removed in GitLab 20.0, planned for May 20, 2027. List the new failure reasons instead.
On our scale this is Act: change a setting or plan before the date. You can stay.
GitLab 19.0 split two failure reasons into more exact ones. The old names are stuck_or_timeout_failure and job_execution_timeout. You can still use them in retry:when, but you get a warning. GitLab plans to remove them in GitLab 20.0, on May 20, 2027.
Here are the facts we checked:
You can stay on GitLab. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
GitLab is the main source for this page. GitLab has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Pipelines that list the old values: Must use the new values before GitLab 20.0.
The date to remember is May 20, 2027. Make the change before then.
A few tips:
If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.
If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
No questions collected yet.
Thanks.
Run SaaS spend at work? Get these changes before the invoice
Arrivals · for builders
People on GitLab CI jobs that retry on the old timeout reasons can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.
Listing is free. An editor checks it. Not ranked. Not paid.
One email when we publish a checked change in the category you pick. No account needed.
One email on Mondays: the gates in the next 14 days, with the first step for each.