Hello since the update on April 3rd, 2025 our pipelines cannot be triggered manually anymore.
Even the existing ones cannot be cancelled and seems to be stuck running.
Whenever I tried to cancel an existing pipeline / trigger a new one using manual trigger it always shows
[Network Error] Failed to fetch. Which was not the case before.
4 Likes
I am also getting this error [Network Error] Failed to fetch
Need a fix here, CCI staff.
+1. I’m receiving 500 & 404 errors and noticing sporadic behavior (logouts & forced reauths, empty pages, etc) from the app. Additionally, I can’t manually trigger pipelines anymore. Please assist.
1 Like
Same, still an incident ongoing IMO.
My pipelines are not triggering which is the same behaviour as the incident you just resolved. At least from this side.
2 Likes
Commits also aren’t triggering. We’re stuck.
+1 here, seems like the issue marked as resolved recently was not really resolved
1 Like
They just declared an incident for this issue
That issue description doesnt seem to encompass all I’m experiencing though. No workflows are triggering or reporting their status either.
4 Likes
UI loading isn’t a problem for us here. It seems like it’s more so executor network issues.
2 Likes
Sorry for the delayed response folks, let me know if you are still seeing issues. The two incidents we opened tonight should be resolved at this point.
Apologies for the interruption of service