Loading

MuleSoft Application Deployment Fails with error: "Readiness Probe Failed 409: API xxx: Not Ready. Awaiting for Successful API Tracking"

Publiseringsdato: Apr 23, 2026
Beskrivelse

When deploying an application, the deployment failed. The following error message is reported in the application log:

Readiness probe failed: 409: API <API_ID>: Not Ready. Awaiting for successful API tracking.

This error occurs when the Mule runtime is unable to peer API instance in MuleSoft API Manager. Common causes include:

  • Missing or incorrect Client ID / Client Secret — An application tries to communicate the API Instance defined in an Environment in an Organization by given cleint_id and client_secret. If the ID and Secret does not match for the Environment or Organization, the application fails to communicate the target API instance in MuleSoft API Manager.

  • Incorrect API AutoDiscovery configuration — The API ID specified in <api-gateway:autodiscovery apiId="..."> does not match the API instance ID in MuleSoft API Manager.

    Løsning

    To resolve the error: Readiness probe failed: 409: API <API_ID>: Not Ready. Awaiting for successful API tracking. , please review following points.

    1. Verify Client ID and Client Secret
      Ensure that the client_id and client_secret you provided are correct. The credentials must match the organization or environment of the API instance in MuleSoft API Manager that the application is attempting to peer with. Please see documentation link [1][2] to configure the correct credential.

    2.  Verify API AutoDiscovery Configuration
      Confirm that the API ID configured in the Autodiscovery Element in your Mule Runtime application —  <api-gateway:autodiscovery apiId="...">  — matches the API instance ID shown in MuleSoft API Manager. 

    If the above solutions do not work, please issue a customer case with application logs. In case of you are using Runtime fabric, please upload RTF Lite Report (see documentation link [3] about how to capture RTF Lite Report)

    References

    [1] Configuring Mule Gateway API Autodiscovery in a Mule 4 Application
    https://docs.mulesoft.com/mule-gateway/mule-gateway-config-autodiscovery-mule4

    [2] Configuring Organization Credentials in Mule Runtime 4
    https://docs.mulesoft.com/mule-gateway/mule-gateway-org-credentials-mule4

    [3] What Information to Collect for a MuleSoft Runtime Fabric (RTF) Support Case
    https://help.salesforce.com/s/articleView?id=001116887&type=1

    Knowledge-artikkelnummer

    005318641

     
    Laster
    Salesforce Help | Article