---
schema_version: "1"
id: a3f33a18dc4864052df142d3635d9d2d21c2aacd92abf53a021c72505089ed3f
title: Deployment Error When Configuring API Autodiscovery
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-manager/latest/troubleshooting-config-properties-apiid-error.md
canonical_url: https://docs.mulesoft.com/api-manager/latest/troubleshooting-config-properties-apiid-error
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 6b2fecd1385b3456237d205772933d3ea5561112f47de909fdca7402bf16d8fd
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: API Manager
version: 2.x
is-latest-version: true
---

# Deployment Error When Configuring API Autodiscovery

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

When you configure Mule Gateway for API autodiscovery, you might receive the following "failed to
deploy artifact" error:

```text
org.mule.runtime.deployment.model.api.DeploymentException: Failed to deploy artifact [accounts]
Caused by: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.deployment.model.api.DeploymentInitException: PropertyNotFoundException: Couldn't find configuration property
value for key ${apiId} from properties provider Domain properties - within
resolver Deployment properties trying to process key apiId - within
resolver global-properties configuration attributes trying to process key apiId - within resolver environment properties provider trying to process key apiId - within resolver Deployment properties trying to process key apiId - within resolver External files trying to process key apiId - within resolver Deployment properties trying to process key apiId
```

## Cause

This issue occurs if you did not add the `apiId` property in the `config.properties` file, and
failed to modify the value for the `apiId` attribute in the `api-gateway:autodiscovery` element. The
Autodiscovery process runs on a specific instance of API Manager. For that reason, you must specify
a valid `apiId` of type `long`.

If you deployed a proxy application through API Manager or downloaded the auto-generated proxy, this
setting is automatically configured.

## Solution

To resolve this issue:

1.  Navigate to the config.properties file and append the following property and value pair:

    ```text
    apiId=[your-specific-value]
    ```

2.  In your <api-gateway:autodiscovery> element, set the `apiID` attribute to the `apiId` property
    in the config.properties file:

    ```text
    apiId=${apiId}
    ```

## See Also

- [Configure Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure)

- [Known Issues](https://help.salesforce.com/s/issues)