# Using the Signal Explorer

> Source: https://docs.trailspark.ai/signal-management/signal-explorer

## Accessing Signal Explorer

Navigate to **Signal Explorer** from the main navigation. Requires Owner, Admin, or Editor role.

![Trailspark Signal Explorer](https://docs.trailspark.ai/images/docs/signal-explorer/signal-explorer.png)

## Statistics Cards

Four metrics display at the top:

| Metric | Description |
| - | - |
| **Total Signals** | All signals received |
| **Pending** | Awaiting processing |
| **Processed** | Successfully processed |
| **Failed** | Encountered processing errors |

## Processing Signals

Signals are processed automatically when mapping rules match. To trigger manual processing:

1. Click **Process Signals**
2. Processing runs immediately against all current mapping rules
3. Results display when complete, showing processed/successful/failed counts and duration

Use manual processing when:

- Testing new or updated mapping rules
- Clearing a backlog of pending signals
- Reprocessing after rule changes

## Processed Signals Table

The table displays processed signals in two tabs:

### Processed Tab

| Column | Description |
| - | - |
| **Signal Name** | Rule name or event type |
| **Source** | Signal source system badge |
| **Lead** | Link to the associated lead record (if created) |
| **Processed At** | When processing occurred |
| **Rule** | The mapping rule that processed the signal |

### Failed Tab

| Column | Description |
| - | - |
| **Event Type** | Technical event type |
| **Source** | Signal source system badge |
| **Status** | Processing outcome badge (Failed, Skipped, Permanently Failed) |
| **Error** | Error message (hover for full text) |
| **Failed At** | When processing failed |

## Usage Limits

Alerts display when approaching your plan's Raw Signal or Mapped Signal limits. These appear above the statistics cards.

> [!WARNING]
> Past your plan's ingested signal limit, Trailspark keeps collecting signals at no extra charge up to **twice** the limit, but holds them: paused signals don't update your scores, and they're **deleted at the end of the billing period**. Enable usage overages on a paid plan or upgrade to resume them right away. Beyond twice the limit, webhook endpoints return `429` status codes and new signals are rejected until the next billing period.

## Common Error Messages

| Error | Resolution |
| - | - |
| "No identifying field" | Map email or a user ID in the matching rule |
| "Invalid path" | Check field mapping source paths in the rule |
| "Rule not found" | Create a mapping rule for this signal type |

## Next Steps

- [Creating Signal Mapping Rules](https://docs.trailspark.ai/signal-management/creating-signal-mapping)
- [Editing Signal Mapping Rules](https://docs.trailspark.ai/signal-management/editing-signal-mapping)
- [Signal Archiving](https://docs.trailspark.ai/signal-management/signal-archiving)