> ## Documentation Index
> Fetch the complete documentation index at: https://doc.lucidworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting Platform Signals

Common issues and solutions for Platform signals integration in Lucidworks Search.

## No signals in collection

**Symptom**: The `COLLECTION_NAME_signals_aggr` collection is empty or not populated.

**Diagnosis**:

1. Check whether the collection exists in Lucidworks Search Admin UI:
   * Navigate to Collections.
   * Search for `COLLECTION_NAME_signals_aggr`.

2. Run a query in Query Workbench:
   ```
   q=*:*&fl=query_s,doc_id,type,weight_d,aggr_count_i
   ```

**Common Causes**:

1. **No signals in Platform Signals Store**
   * Beacon is not configured or not tracking events.
   * The Platform aggregation job hasn't run yet.

2. **Signal retrieval not configured**
   * Platform credentials were not provided to Lucidworks Support.
   * Signal retrieval configuration is incomplete.

3. **Collection name mismatch**
   * The collection name doesn't match the Lucidworks Search app name.

**Solution**:

1. Verify signal collection is working:
   * Check the Platform dashboard for signal activity.
   * Verify your [Beacon](/docs/lw-platform/lw-analytics/signals/signals-beacon) or [Platform Signals API](/docs/lw-platform/lw-analytics/signals/signals-api) configuration.

2. Contact Lucidworks Support:
   * Provide your app name and Platform integration details.
   * Include the approximate time when signals should have been retrieved.
   * Lucidworks Support can check signal retrieval logs and processing status.

3. Verify collection name format:
   * The collection name should be `COLLECTION_NAME_signals_aggr`.
   * The name must match your Lucidworks Search app configuration.

## Incorrect signal weights

**Symptom**: Documents are boosted, but weights don't match expected values.

**Diagnosis**:

Query the signals collection to inspect weights, usually in the `weight_d` field.

**Common Causes**:

1. **Formula configuration mismatch**
   * Formula weights in the signal retrieval configuration don't match the Platform formula.
   * The wrong formula name is specified in the Boost with Signals stage.

2. **Field mapping issues**
   * The Rollup Weight Field in the query stage doesn't match the signal document field.

**Solution**:

1. Verify formula configuration matches Platform:
   * Check Platform formula definition.
   * Contact Lucidworks Support to verify signal retrieval configuration.

2. Verify Boost with Signals stage configuration:
   * **Aggregation Type** must match formula name (e.g., `formula1`).
   * **Rollup Weight Strategy** must be `weight_d`.

## Query boosting not working

**Symptom**: Queries execute successfully but results are not boosted based on signals.

**Diagnosis**:

1. Check whether the Boost with Signals stage is enabled in the query pipeline.
2. Run a query with debug enabled: `debug=true`.
3. Review boost parameters in the debug output.

**Common Causes**:

1. **Stage not in pipeline**
   * The Boost with Signals stage is missing or disabled.

2. **Wrong aggregation type**
   * The Aggregation Type in the stage doesn't match the signals formula.

3. **Field name mismatch**
   * The Rollup Field value doesn't match the signal document field names.

4. **Empty signals collection**
   * No matching signals exist for the query.

**Solution**:

1. Add or enable the Boost with Signals stage in the query pipeline.

2. Verify the stage configuration:

   * Aggregation Type: `formula1`
   * Rollup Field: `doc_id`
   * Rollup Weight Strategy: `weight_d`

3. Test with a known query that has signals:
   * Query the signals collection to find a query with aggregated data.
   * Execute that query through the pipeline.
   * Verify boosting is applied in the debug output.

## Slow query performance

**Symptom**: Queries with signal boosting are significantly slower than without.

**Diagnosis**:

Enable query timing and examine the Boost with Signals stage performance:

```
debug=true&debugQuery=true
```

**Common Causes**:

1. **Large number of signals retrieved**
   * The `numSignals` parameter is set too high.

2. **Inefficient signals collection query**
   * Solr Query Parameters are missing or incorrect.

**Solution**:

1. Tune Boost with Signals stage parameters:
   * Reduce `numSignals` to a reasonable value (50-100).
   * Reduce `numRecommendations` if appropriate.

2. Optimize signals collection:
   * Make sure appropriate fields are indexed.
   * Consider adding filters to limit signal retrieval scope.

## Authentication or integration issues

**Symptom**: Signal retrieval appears to have stopped or never started.

**Common Causes**:

1. **Integration credentials expired or invalid**
   * The Client ID or Secret are incorrect.
   * The integration was deleted or modified in Platform.

2. **Configuration mismatch**
   * Integration name doesn't match.
   * Platform application ID is incorrect.

**Solution**:

Contact Lucidworks Support with the following information:

* Your Lucidworks Search instance name
* Platform integration name
* App name where signals should appear
* Time period when the issue started
* Any recent changes to Platform configuration

Lucidworks Support can verify the integration configuration and check signal retrieval logs for errors.

## Getting help

If you continue to experience issues after following this guide, contact Lucidworks Support with the following information:

1. **Environment details**:
   * Lucidworks Search instance name
   * App name
   * Collection name

2. **Platform integration details**:
   * Platform application name and ID
   * Integration name
   * Signal Store configuration

3. **Symptoms observed**:
   * When the issue started
   * Error messages in the UI
   * Example queries that show the problem

4. **Configuration details**:
   * Boost with Signals stage configuration
   * Expected vs. actual behavior

Lucidworks Support can access signal retrieval logs and verify the configuration on your behalf.

## Related topics

* [Configure Platform Signals](/docs/lucidworks-search/04-move-data-in/platform-signals/configuration)
* [Boost with Signals Stage](/docs/lucidworks-search/07-improve-your-queries/boosting/boost-with-signals)
* [Platform Signals](/docs/lw-platform/lw-analytics/signals/overview)