# Restart a build check in a PR that failed due to a network issue **URL:** \ **Category:** Travis CI Discussions & Feedback\ **Tags:** github-build-check\ **Created:** [August 12, 2019, 5:50am UTC](https://travis-ci.community/t/restart-a-build-check-in-a-pr-that-failed-due-to-a-network-issue/4689 "2019-08-12T05:50:39Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [August 12, 2019, 7:58am UTC](https://travis-ci.community/t/restart-a-build-check-in-a-pr-that-failed-due-to-a-network-issue/4689/2 "2019-08-12T07:58:04Z")
As a contributor, you can create an empty commit with `git commit --allow-empty` and push it to trigger a rebuild. PRs intentionally disallow build restarting to prevent contributors from smuggling unreliable code in. * * * The specific problem that failed that build is > [@Maven Central dependency resolution constantly fails with "connect timed out"](https://travis-ci.community/t/maven-central-dependency-resolution-constantly-fails-with-connect-timed-out/4582): > > Hello, We’ve had problems over the last few days with Maven dependencies failing to be retrieved from Maven Central due to connection timeouts. My build is now failing 100% of the time with this same “connect timed out” error from the Maven Central repo. Other builds are failing with the same issue. Could this is related to rate-limiting from Maven Central? An example of a failing (private) build is this here: [https://travis-ci.com/Swirrl/muttnik/builds/121991654](https://travis-ci.com/Swirrl/muttnik/builds/121991654) I have tried extending the … --- _[View the full topic](https://travis-ci.community/t/restart-a-build-check-in-a-pr-that-failed-due-to-a-network-issue/4689)._