# GitHub status not posted on commits on repositories using legacy Service integration

**URL:** <https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798>\
**Category:** Travis CI Discussions & Feedback\
**Created:** [March 25, 2020, 7:31pm UTC](https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798 "2020-03-25T19:31:16Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [April 10, 2020, 5:51pm UTC](https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798/14 "2020-04-10T17:51:43Z")

</div>

As I stated earlier, the incident concerns reaching the GitHub API rate limit. That issue is resolved, thanks to the (temporary) raise granted by GitHub.

There are other cases where we fail to post statuses for various reasons (chief among them is having tokens being out of sync). These may still occur, but these would have occurred even before the incident.

> [@bvliu](#):
>
> Is the solution here to migrate from legacy to GitHub Apps?

I encourage you to do so.

---

_[View the full topic](https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798)._