Help debugging cancelled runners on main branch

Дата публикации: 20-07-2026 18:37:19

I’ve started to notice some runs marked as “Failed/Failing” which aren’t.
One job has 6 parallel runners and for some reason some runners are getting cancelled. This is on the main branch so the “auto-cancel” feature should not apply. I don’t see any timeouts being hit- the runs finish in around 30mins and get consistent output. Nothing has changed that I know of but this started around July 7th.
So this could be 2 separate problems:
Parallel runners are getting cancelled on the main branch
Cancelled runners should are showing as “failed”
1 post - 1 participant
Read full topic

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	Workflow cancellation reliability improvements	0	5.59	03-07-2026
2	New UI, Cancel button lacks transparency	0	7.3	20-07-2026
3	Post Incident Report: July 2, 2026 - Outage impacting web experience and pipelines starting	0	11.86	10-07-2026
4	Post Incident Report: July 20, 2026 - Errors with Github API Delaying Workflows	0	10.94	23-07-2026
5	Security notice and deprecation: standalone circleci-mcp-server	0	8.32	20-07-2026
6	Post Incident Report: 2026-07-13 Network Routing Issues Cause Intermittent macOS Job Failures	0	11.1	16-07-2026
7	Downstream job triggers even if one of the jobs in its required job group fails	0	8.51	24-07-2026
8	Post Incident Report: June 23, 2026 - Delays starting Docker jobs	0	10.34	27-06-2026
9	UI Bug: Runner Inventory page is not scrollable	0	11.99	23-07-2026
10	Our support portal is changing— here’s what to know	0	6.76	24-07-2026

Классификация: Пресс-релизы. Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 7.17. Источник: discuss.circleci.com.