---
schema_version: "1"
id: be4e5bf0cf04c5958ccfd99f82ff1ed6825282404932420f1c7c91843cb80265
title: Troubleshooting Object Store Connector
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/object-store-connector/latest/object-store-connector-troubleshooting.md
canonical_url: https://docs.mulesoft.com/object-store-connector/latest/object-store-connector-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 159b9afadb855147c556d8f240c0acb2fb12b5a63740adc5b415c92d58c050b0
description: MuleSoft Documentation Site
release: "1.3"
latest: true
---
---
product: Object Store Connector
version: 1.3
is-latest-version: true
---

# Troubleshooting Object Store Connector

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

To troubleshoot Anypoint Connector for Object Store (Object Store Connector), become familiar with
the information about enabling verbose logging and interpreting commonly thrown messages.

## Enable Verbose Logging

To get a better understanding of why an application’s interaction fails with Object Store Connector,
temporarily enable verbose logging for the connector.

Remember to always disable the enhanced verbosity after troubleshooting, because it affects your
Mule application performance.

To enable verbose logging in the configuration file:

1.  Access Anypoint Studio and navigate to the **Package Explorer** view.

2.  Open your application’s project name.

3.  Open the `src/main/resources` path folder.

4.  Open the `log4j2.xml` file inside the folder.

5.  Add an `<AsyncLogger>` tag inside the `<Loggers>` tag:

    ```xml
    <Loggers>
    	...
    	 <AsyncLogger name="org.mule.extension.objectstore" level="DEBUG"/>
    	...
    </Loggers>
    ```

6.  Save your application changes.

7.  Click the project name in **Package Explorer** and then click **Run** > **Run As** > **Mule
    Application**.

## Understand Common Throws

Here is a list of common throw messages and how to interpret them:

- OS:KEY\_ALREADY\_EXISTS

  The Mule app tries to store an object, but the object store already has a value for that key.

- OS:STORE\_NOT\_AVAILABLE

  Cannot access the object store at this time.

- OS:INVALID\_KEY

The supplied key is invalid. Keys cannot be null nor blank.

- OS:KEY\_NOT\_FOUND

The object store must access a value, but the supplied key doesn’t exist in that store.

- OS:NULL\_VALUE

A null value was supplied to the object store. Null values are not supported.

## See Also

- [Object Store Connector Reference](https://docs.mulesoft.com/object-store-connector/latest/object-store-connector-reference)

- [Salesforce Help](https://help.salesforce.com)

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