# Troubleshooting Alemba Discovery

## Connector diagnostics

{% hint style="danger" %}
This is currently Draft documentation and may change before being published.
{% endhint %}

The connector has the facility to trace information. The data can be obtained through Polling tracing or Application tracing.

* Authentication failures – check AIH Basic Auth and Lansweeper API token
* API rate limit (150 requests/minute) – AIH introduces delay to avoid exceeding limits
* Array fields – flattened into comma-separated values; only first item imported in some cases
* Deleted assets – may require filter logic in AIH to exclude removed records
* Connector Builder deletion – avoid deleting asset types once created (\*Known Issue: risk of losing all mappings below the entry deleted)

#### Authentication Failures

* Verify username/password in the authentication function
* Check that Basic Authentication header is properly formatted

#### 2. Token Retrieval Issues

* Verify PowerShell script path and permissions
* Check Azure credentials and connectivity
* Review script output for errors

#### 3. Lansweeper API Errors

* Verify site ID and integration ID
* Check Lansweeper API connectivity
* Review API response for error details

#### 4. Software ID Format Issues

* Ensure software ID follows "software::publisher" format
* URL encode special characters in software names
* Verify software exists in Lansweeper

#### 5. Pagination Issues

* Ensure $nextpage parameter is properly formatted
* Check that pagination URLs are correctly constructed

#### Debug Information

The flow includes multiple debug nodes that provide detailed information:

* Request/response payloads
* Authentication status
* API call details
* Error messages

Enable debug nodes in Node-RED to troubleshoot issues.