Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Troubleshoot the webhook for failed builds or a hanging job

Focus mode
Troubleshoot the webhook for failed builds or a hanging job - AWS CodeBuild

Issue:

The webhook you set up in Tutorial: Configure a CodeBuild-hosted Buildkite runner isn't working or your workflow job is hanging in Buildkite.

Possible causes:

  • Your webhook job.scheduled event might be failing to trigger a build. Review the Response logs to view the response or error message.

  • Your CodeBuild build fails before starting the Buildkite self-hosted runner agent to handle your job.

Recommended solutions:

To debug failed Buildkite webhook events:

  1. In your Buildkite organization settings, navigate to Notification Services, select your CodeBuild webhook, and then find the Request Log.

  2. Find the job.scheduled webhook event associated with your stuck Buildkite job. You can use the job ID field within the webhook payload to correlate the webhook event to your Buildkite job.

  3. Select the Response tab and check the response body. Verify that the Response status code is 200 and the Response body doesn’t contain any unexpected messages.

    Response for the webhook.
PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.