GitLab webhook stopped working so I deleted it and... now I can't recreate it


CodeCov stopped producing the codecov/patch and codecov/project GitLab jobs. When using ./codecov-linux --dir xxx -F yyyy it now complained with Error!: Error: Error uploading to Error: Error uploading to Codecov: Error: Not Found. So I decided to delete the hook from GitLab, and recreate it by pressing the button in Codecov Reset webhook, without success.

Commit SHAs

I can’t since I removed all the project data and the Webhook from GitLab thinking that starting fresh and clean, deactivating, revoking OAuth tokens and doing it all again would fix the problem.

Now I can’t re-create the Webhook with the Reset webhook action, it complains with Webhook with id 8089382 does not exist


Codecov Output

$ ./codecov-linux --dir coverage/apps/studio -F studio
     _____          _
    / ____|        | |
   | |     ___   __| | ___  ___ _____   __
   | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |  __/ (_| (_) \ V /
    \_____\___/ \__,_|\___|\___\___/ \_/
  Codecov report uploader 0.1.0
=> Project root located at: /builds/watchity/frontend
Searching for coverage files...
=> Found 3 possible coverage files:
Processing cobertura-coverage.xml...
Processing coverage-final.json...
Processing coverage-final.json...
Detected GitLab CI as the CI provider.
Pinging Codecov:*******&branch=develop&build=1445079675&build_url=&commit=243b9b0a34edca52a19a014dac716197751094c6&job=&pr=&service=gitlab&slug=watchity/frontend&name=&tag=&flags=studio&parent=
Error!: Error: Error uploading to Error: Error uploading to Codecov: Error: Not Found

Additional Information

Well now I think I am stuck in a limbo where I can’t recreate anything. Could someone reset everything from that repository to factory defaults, so I can recreate it all anew?

I created another Webhook manually, it’s ID is 8090123.

Shooting at

How could I align my account to this changes?

@docwhite apologies, I think this was an issue with our system, not with webhooks. Have you been able to try again as we patched the issue above?