Loading

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

Дата публикации: Jun 16, 2026
Описание

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 client_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.

Missing Mule Properties for Non-US Control Plane

When using a non-US control plane (e.g., EU, Canada),  additional Mule runtime properties such as anypoint.platform.base_uri and anypoint.platform.analytics_base_uri may need to be explicitly configured (please see Ref[3] for detailed instruction). Without these settings, the Mule runtime cannot reach the correct control plane endpoint, resulting in this error.

    Решение

    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 Ref [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. 

    3. Verify Mule Properties for Non-US Control Plane

    If you are using a non-US control plane (e.g., EU, Canada), please confirm that Mule runtime properties described in Ref [3] are configured. The additional properties that may need to be configured include anypoint.platform.base_uri and anypoint.platform.analytics_base_uri.

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

    References

    [1] Configuring Mule Gateway API Autodiscovery in a Mule 4 Application
    [2] Configuring Organization Credentials in Mule Runtime 4
    [3] Configuring Mule Properties to Access Control Planes
    [4] What Information to Collect for a MuleSoft Runtime Fabric (RTF) Support Case

    Номер статьи базы знаний

    005318641

     
    Загрузка
    Salesforce Help | Article