# Status checks randomly broken **URL:** \ **Category:** Travis CI Discussions & Feedback\ **Tags:** github-integration, travis-build, bug\ **Created:** [March 29, 2020, 11:59am UTC](https://travis-ci.community/t/status-checks-randomly-broken/7876 "2020-03-29T11:59:15Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Yuri6037](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/yuri6037/32/4117_2.png) [@Yuri6037](https://travis-ci.community/u/Yuri6037)\ **Post date:** [March 29, 2020, 11:59am UTC](https://travis-ci.community/t/status-checks-randomly-broken/7876/1 "2020-03-29T11:59:15Z")
Hello, randomly Travis CI status checks on PRs gets never received. On the PR request I have that message: **continuous-integration/travis-ci** Expected — Waiting for status to be reported. However in Travis CI the build has succeeded but GitHub skipped it. ---
**Author:** ![bobbrow](https://avatars.discourse-cdn.com/v4/letter/b/b77776/32.png) [@bobbrow](https://travis-ci.community/u/bobbrow)\ **Post date:** [March 31, 2020, 4:40pm UTC](https://travis-ci.community/t/status-checks-randomly-broken/7876/2 "2020-03-31T16:40:08Z")
My PR builds are not getting a status update on GitHub either. Example: PR: [https://github.com/microsoft/vscode-cmake-tools/pull/1151](https://github.com/microsoft/vscode-cmake-tools/pull/1151) The CI build completed: [https://travis-ci.org/github/microsoft/vscode-cmake-tools/builds/669257461?utm\_medium=notification&utm\_source=github\_status](https://travis-ci.org/github/microsoft/vscode-cmake-tools/builds/669257461?utm_medium=notification&utm_source=github_status) ---
**Author:** ![AenBleidd](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/aenbleidd/32/4118_2.png) [@AenBleidd](https://travis-ci.community/u/AenBleidd)\ **Post date:** [March 31, 2020, 11:03pm UTC](https://travis-ci.community/t/status-checks-randomly-broken/7876/3 "2020-03-31T23:03:43Z")
I see this also: [https://github.com/BOINC/boinc/pull/3549](https://github.com/BOINC/boinc/pull/3549) ---
**Author:** ![Yuri6037](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/yuri6037/32/4117_2.png) [@Yuri6037](https://travis-ci.community/u/Yuri6037)\ **Post date:** [June 14, 2020, 4:48pm UTC](https://travis-ci.community/t/status-checks-randomly-broken/7876/4 "2020-06-14T16:48:11Z")
I think I will move to GitHub Actions for PR status checks cause it’s really annoying to have to disable branch securities then force merge then rearm branch security ---
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [June 14, 2020, 5:11pm UTC](https://travis-ci.community/t/status-checks-randomly-broken/7876/5 "2020-06-14T17:11:43Z")
> [@Known Issue: Travis CI reports "Expected - Waiting for status to be reported" on the GitHub Status API, but the status never arrives](https://travis-ci.community/t/known-issue-travis-ci-reports-expected-waiting-for-status-to-be-reported-on-the-github-status-api-but-the-status-never-arrives/1154): > > Symptom Your repository stopped receiving status updates. In your PR, you see something like this: Explanation As part of our gradual migration to the Travis CI GitHub App, that now uses GitHub Checks to report build statuses, we kept posting both GitHub Checks as well as the old commit statuses for some time to not break repositories using the commit statuses in their protected branches settings and give time to do the change to use the new Che… ---
**Author:** ![Yuri6037](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/yuri6037/32/4117_2.png) [@Yuri6037](https://travis-ci.community/u/Yuri6037)\ **Post date:** [June 14, 2020, 5:23pm UTC](https://travis-ci.community/t/status-checks-randomly-broken/7876/6 "2020-06-14T17:23:09Z")
Already checked this post but on my repository only the > [@Yuri6037](#): > > continuous-integration/travis-ci exists in Branch protection. ---
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [June 24, 2020, 2:30pm UTC](https://travis-ci.community/t/status-checks-randomly-broken/7876/7 "2020-06-24T14:30:39Z")
This means that you don’t have the newer Github App integration installed. Check if you have “Travis CI” in [https://github.com/settings/installations](https://github.com/settings/installations) and if it’s enabled for all repositories. Normally, it’s installed when you grant Travis access to your Github account. So you can revoke grants at [https://github.com/settings/applications](https://github.com/settings/applications) and sign up at Travis again. If you are using [https://travis-ci.org](https://travis-ci.org) (you didn’t specify that or give any links so can’t say), you may need to [reset Travis integration for each affected project](https://travis-ci.community/t/pushes-wont-trigger-new-builds-anymore-after-the-project-has-been-inactive-for-a-long-time/5716/2) to get the new logic. You might also need to fully migrate affected projects to [https://travis-ci.com](https://travis-ci.com) at [https://travis-ci.com/account/migrate](https://travis-ci.com/account/migrate) (I had a project that was enabled at both sites; this typically doesn’t work so well). ---
**Author:** ![Yuri6037](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/yuri6037/32/4117_2.png) [@Yuri6037](https://travis-ci.community/u/Yuri6037)\ **Post date:** [June 24, 2020, 3:42pm UTC](https://travis-ci.community/t/status-checks-randomly-broken/7876/8 "2020-06-24T15:42:34Z")
I’m using [travis-ci.org](http://travis-ci.org) as my project is open source. I already had reset the github apps for the reporsitory and it is still random. The thing is it’s not always broken it’s just randomly broken. That means some times status checks are reported sometimes not. Anyway now the project is using GitHub Actions to validate the state of PRs and so far no more issues. I’ll keep travis but only as a way to quickly broadcast coverage data (I made the build script much lighter as the core is now migrated to GitHub Actions) and also maintain public build logs (which is a defect of GitHub Actions)