---
title: Connector troubleshooting
description: It can be difficult to determine if the root cause of a problem is at the ICF or connector level, or at the application level.
component: openicf
page_id: openicf:connector-dev-guide:troubleshooting
canonical_url: https://docs.pingidentity.com/openicf/connector-dev-guide/troubleshooting.html
keywords: ["Logs", "Troubleshooting"]
section_ids:
  logs: Logs
  custom_connector_required_version_pattern: Custom connector required version pattern
---

# Connector troubleshooting

## Logs

It can be difficult to determine if the root cause of a problem is at the ICF or connector level, or at the application level.

The ICF API sets the `LoggingProxy` at a very high level. You can consider the Logging Proxy as the *border* between the application (IDM) and the ICF framework.

For more information about logging, refer to [Connector logs](../connector-reference/icf-logs.html).

## Custom connector required version pattern

If your custom connector configuration fails to display in the admin UI, make sure that it's using 4-digit versioning. The admin UI expects this type of version pattern. For example:

```
1.5.0.0
```