Known Issue: Travis CI reports "Expected - Waiting for status to be reported" on the GitHub Status API, but the status never arrives



Your repository stopped receiving status updates. In your PR, you see something like this:


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 Checks instead.

As of October 4th, those repositories on which are managed by GitHub Apps no longer receive updates to the GitHub Commit Status API. Instead, Build Statuses will be posted to the GitHub Check Runs API.


To fix this issue, update your repositories using protected branches to require GitHub Checks as follows:

  1. Go to the repository’s Branch Settings page (
  2. In the “Branch Protection Settings” section, click “Edit” for a protected branch
  3. Scroll down to the second box, “Require status checks to pass before merging.” Select either “Travis CI - Pull Request” or “Travis CI - Branch” or both. (Note: “continuous-integration/travis-ci” is the Status API event which is deprecated)
  4. Save your changes

Original post here:

pinned #2
unpinned #3
pinned globally #4

That’s dec 16


Expected released dec 16 but there is a error


This problem does not seems too be solved. I’m following these instructions to the letter, and there is no change whatsoever. This is the PR. Has there been any change lately on how things are running in Travis?


@dalonsoa appears to have been disabled.

1 Like

@BanzaiMan, thank you very much for the information. Yesterday, I transferred the repo to an organisation I am owner and didn’t realised that was affecting Travis. Now it is enabled again.


FTR I’m seeing this sometimes (not consistently).

Also: I’ve hit this with other GitHub Apps which I’m developing so I assume the problem might be on the GitHub’s side.


@webknjaz Oh, seeing this unconsistently is most curious as this case normally applies to people that have switched from webhooks to GitHub Apps at Travis CI and had a protected branch setup.
Do you have any more details on the behaviour you’re seeing / you’ve noticed? It may be something else.