# Codecov status stuck at "waiting for status to be reported" **URL:** \ **Category:** Support\ **Created:** [August 2, 2019, 3:52am UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406 "2019-08-02T03:52:28Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![billcchung](https://avatars.discourse-cdn.com/v4/letter/b/919ad9/32.png) [@billcchung](https://community.codecov.com/u/billcchung)\ **Post date:** [August 2, 2019, 3:52am UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/1 "2019-08-02T03:52:28Z")
We’re facing the same issue as [Codecov status stuck at "waiting for status to be reported" on github](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported-on-github/341) again, Not sure if someone can help? @drazisil? Thanks! ---
**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\ **Post date:** [August 2, 2019, 2:25pm UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/2 "2019-08-02T14:25:39Z")
Hi @billcchung We are further investigating this, seems it’s not as fixed as we hoped. Can you create a ticket for me? Mention that I asked for it and I can attach it to our internal issue after confirming it’s the same case. ---
**Author:** ![rarkins](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/rarkins/32/218_2.png) [@rarkins](https://community.codecov.com/u/rarkins)\ **Post date:** [August 3, 2019, 2:01am UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/3 "2019-08-03T02:01:17Z")
This is affecting up to 1/3 to 1/2 of our PRs for the last month. I tried sending details to support but they turned us away as we are an open source project with no support plan. Coverage is sent to codecov but codecov fails to set the status checks on GitHub. We have codecov as a required status check on PRs so obviously can’t continue like this. ---
**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\ **Post date:** [August 3, 2019, 2:56am UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/4 "2019-08-03T02:56:51Z")
@rarkins can you provide the ticket number and I’ll take a look? ---
**Author:** ![abitrolly](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/abitrolly/32/219_2.png) [@abitrolly](https://community.codecov.com/u/abitrolly)\ **Post date:** [August 3, 2019, 4:58am UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/5 "2019-08-03T04:58:13Z")
The same issue here - [Add `docker build` testing to Travis by abitrolly · Pull Request #799 · fedora-infra/anitya · GitHub](https://github.com/release-monitoring/anitya/pull/799) - build is passed, but `codecov` status on GitHub is still pending after 14 hours. Force pushes were taking place during work on this PR. Hope that helps. ---
**Author:** ![rarkins](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/rarkins/32/218_2.png) [@rarkins](https://community.codecov.com/u/rarkins)\ **Post date:** [August 4, 2019, 11:17am UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/6 "2019-08-04T11:17:22Z")
@drazisil I’m not sure if it was assigned a ticket number as it’s an open source project without paid plan. I understand your need to partition off support requests and don’t mind having the information exchange here instead if you prefer. Basic facts: - Node.js project (istanbul coverage) - Using Node.js 10 and 12 builds in parallel on CircleCI - No token added on CircleCI as it’s said to not be necessary - Using `bash <(curl -s https://codecov.io/bash) -Z -C $CIRCLE_SHA1` By my estimate, around 30% or more of PRs lately have been missing the status check on GitHub. Retrying the CircleCI builds does not always result in it being fixed either. When I check CircleCI logs or Codecov UI, I’ve always seen a result there although sometimes there is a log of CircleCI failing to push the first time. ---
**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\ **Post date:** [August 5, 2019, 12:34pm UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/7 "2019-08-05T12:34:55Z")
@rarkins I bumped your user level so you should be able to post links now. Let’s address in the ticket, then we can bring the results back here for the community. ---
**Author:** ![billcchung](https://avatars.discourse-cdn.com/v4/letter/b/919ad9/32.png) [@billcchung](https://community.codecov.com/u/billcchung)\ **Post date:** [August 13, 2019, 3:39am UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/8 "2019-08-13T03:39:53Z")
@drazisil Sorry for the late reply, we’re seeing this again, not sure if there’s already an existing ticket so we can track the progress? if not I can create one. Thanks ---
**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\ **Post date:** [August 13, 2019, 12:47pm UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/9 "2019-08-13T12:47:11Z")
@billcchung Let’s get a ticket created so I can see what the cause is, and verify if it’s the same issue, please. ---
**Author:** ![davclark](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/davclark/32/354_2.png) [@davclark](https://community.codecov.com/u/davclark)\ **Post date:** [October 25, 2019, 7:16pm UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/10 "2019-10-25T19:16:44Z")
I’ve experienced this issue sporadically, but it has been hitting us harder recently. I see various discussions about “waiting for status…” on github and “Unable to find report…” on codecov. Here’s the PR I’m currently struggling with: > **[Code coverage done right.](https://app.codecov.io/gh/gigantum/gigantum-client/compare/1076)** > > Hosted coverage report highly integrated with GitHub, Bitbucket and GitLab. Awesome pull request comments to enhance your QA. Is there a fix for missing codecov? ---
**Author:** ![chuck.imperato](https://avatars.discourse-cdn.com/v4/letter/c/5fc32e/32.png) [@chuck.imperato](https://community.codecov.com/u/chuck.imperato)\ **Post date:** [October 28, 2019, 4:12pm UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/11 "2019-10-28T16:12:47Z")
We’re still having the same issue. At this point we are going to move away from codecov. Every time we submit code to go into our default branch this happens. It is killing our productivity. ---
**Author:** ![elucidsoft](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@elucidsoft](https://community.codecov.com/u/elucidsoft)\ **Post date:** [October 29, 2019, 12:02am UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/12 "2019-10-29T00:02:47Z")
Same issue here, also going to have to look for alternatives. ---
**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\ **Post date:** [October 30, 2019, 3:30pm UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/13 "2019-10-30T15:30:59Z")
I’m going to share my response here and close this thread so I can track this issue in one place: > [@Unable to find report content in the storage archive](https://community.codecov.com/t/unable-to-find-report-content-in-the-storage-archive/641/6): > > Thank you for the reports, everyone. We are investigating this, since it doesn’t happen for everyone it’s being hard to track down. We are seeing that, for those of you it is affecting, that it’s happening very often, so I completely understand your frustration. Couple of questions: Did this ever work correctly for you, and if so, do you know roughly when it started happening? Can you think of any changes you made around this time? ---
**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\ **Post date:** [October 30, 2019, 3:31pm UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/14 "2019-10-30T15:31:05Z")
Closed on October 30, 2019, 3:31pm UTC ---
**Author:** ![jerrod](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/jerrod/32/41_2.png) [@jerrod](https://community.codecov.com/u/jerrod)\ **Post date:** [November 5, 2019, 6:05pm UTC](https://community.codecov.com/t/codecov-status-stuck-at-waiting-for-status-to-be-reported/406/15 "2019-11-05T18:05:20Z")
Hey all, thanks for your contributions and apologies for the issue. For those on the thread for “Unable to find report content in storage archive” in last two weeks: We started an open issue tracker on this here: [CLOSED ISSUE INVESTIGATION: Report stuck in processing + Unable to find report content in storage archive](https://community.codecov.com/t/open-issue-investigation-report-stuck-in-processing-unable-to-find-report-content-in-storage-archive/670) This is affecting about 1% of users. We are rapidly looking for a root cause fix or a workaround we can deliver to you all. More updates to come on the thread above.