Circle CI stopped triggering on pushes to github

Build Environment
1

I’ve read this similar thread here:
https://discuss.circleci.com/t/troubleshooting-when-circle-doesnt-build-after-pushes-to-github/12414/5

but applying the suggestion made no difference. My projects were fine 2 days ago, but now pushes to github don’t trigger circle CI builds anymore on any projects (tested 2), and circle CI doesn’t even reflect the existence of the new commits on the branches. My credits are all fine as well. What should I do to fix this?

1 Like
2

Can you send a link to your CircleCI pipeline to sebastian@circleci.com and I can take a look

3

Thanks Sebastian, I sent you an email with a link to an older pipeline that hasn’t triggered since.

4

Hey @sebastian-lerner, I am having a similar issue with our CircleCI pipelines. Everything seemed to be running fine untila bout 5 days ago and since then any pushers to PRs or even merges into main are not triggering any workflows to start. Nothing has changed in our circleci config file and I am struggling to find the issue.

When attempting to set up a new trigger in circleci via Github it says “No configuration to run available” so I wonder is it not seeing the config file and why this could be occuring?

2 Likes
5

Im having the same issue. It worked fine 2 days ago. I have been using it for the last 2 months and didnt make any configuration change neither on CircleCi, Github, ssh keys or the circleci/config.yml file. Please check the issue.

1 Like
7

I tried again today (15 hrs later from my last try) and it worked right.

8

@ignacioplanella and @sean-hickey-wf , would you mind confirming that the issue is resolved for you too?
And could you also share your projectID with me - either by DM on here or by email to benedetta@circleci.com? We want to make sure we understand what happened.

9

Hey Benny,

I was able to fix the problem by:

  1. Unfollowing the project
  2. deleting the trigger
  3. following the project again and creating a new trigger with a new ssh key

I don’t know why this was required but by doing all of this we have our ci/cd pipelines working again

1 Like