# Four repos work fine, one does not and I don't know why

**URL:** <https://community.codecov.com/t/four-repos-work-fine-one-does-not-and-i-dont-know-why/657>\
**Category:** Support\
**Created:** [November 3, 2019, 5:01am UTC](https://community.codecov.com/t/four-repos-work-fine-one-does-not-and-i-dont-know-why/657 "2019-11-03T05:01:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RobinHankin](https://avatars.discourse-cdn.com/v4/letter/r/fbc32d/32.png) [@RobinHankin](https://community.codecov.com/u/RobinHankin)\
**Post date:** [November 3, 2019, 5:01am UTC](https://community.codecov.com/t/four-repos-work-fine-one-does-not-and-i-dont-know-why/657/1 "2019-11-03T05:01:52Z")

</div>

### Description

hi there, I love codecov to bits, and four of my repos are fine but one is not working:

> **[Code coverage done right.](https://app.codecov.io/gh/RobinHankin)**
>
> Hosted coverage report highly integrated with GitHub, Bitbucket and GitLab. Awesome pull request comments to enhance your QA.

see how wedge, mvp, freealg, spray repos work fine but lorentz does not. What am I doing wrong?

### Repository

Everything is public on github,

> **[RobinHankin - Overview](https://github.com/RobinHankin)**
>
> pushing the boundaries of R in non-statistical contexts - RobinHankin

---

<div class="post-metadata">

**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:03pm UTC](https://community.codecov.com/t/four-repos-work-fine-one-does-not-and-i-dont-know-why/657/2 "2019-11-05T18:03:32Z")

</div>

Hey @RobinHankin, thanks for your contribution and apologies for the issue.

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.