---
title: "How can I fix webhook issues in Pipelines?"
date: "2025-05-08T09:19:06+00:00"
summary: "Troubleshoot and resolve webhook issues in Pipelines with our guide on error messages and solutions for seamless code deployment."
image:
type: "article"
url: "/acquia-cloud-platform/help/69006-how-can-i-fix-webhook-issues-pipelines"
id: "466b0ff9-34fe-4216-813b-9b04ccae9c2e"
---

*   The following error occurs if you experience a failed code-deploy task due to a webhook connection failure:
    
        Acquia can't reach the webhook destination: #{webhook.url}
        Expected([200, 201, 202, 204]) <=> Actual(403 Forbidden)
    
    The error occurs if Pipelines is not responding. Acquia recommends you to check the [Acquia Status](https://status.acquia.com/) page and try again later. If the issue persists, [contact Acquia Support](/node/55874#contact-acquia-support).
    
*   The following error occurs if the direct switch from Bitbucket or GitHub to the Acquia Git repository fails, which can happen due to missing webhooks:
    
        Danger! 400 : {"success":false,"message":"Could not locate any webhooks","error":"Could not locate any webhooks"}
    
    To recreate the missing webhooks:
    
    1.  Switch to a different provider.   
        For example, if you use Bitbucket, switch to GitHub.
    2.  Switch to Acquia Git.

Note

After you fix any detected issues with any pipeline jobs, run the `start` command again to restart the build.