# Editing Signal Mapping Rules

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

## Accessing the Edit Form

1. Navigate to **Signal Mapping** > **Signal Rules** tab
2. Find the rule and click **Edit**
3. The form loads with current values

All fields from rule creation are editable: rule details, conditions, and field mappings.

## Impact of Changes

> [!WARNING]
> Changes only affect signals processed after saving. Previously processed signals retain their original mappings unless you enable reprocessing.

| Change Type | Effect |
| - | - |
| More restrictive conditions | Fewer signals match going forward |
| Less restrictive conditions | More signals match going forward |
| New field mapping | Future signals populate the new field |
| Changed source path | Different data extracted from future signals |
| Removed mapping | Field no longer populated from new signals |
| Priority change | Alters which rule matches first when conditions overlap |

## Previewing Changes

After modifying conditions, click **Preview Matching Signals** to verify the updated match count before saving.

## Reprocessing Signals

To apply updated rules to already-processed signals:

**From the edit form**: Enable the **Reprocess Matching Signals** toggle before saving. A background job reprocesses matching signals with the updated mappings.

**From Signal Explorer**: Navigate to Signal Explorer and click **Process Signals** to reprocess pending signals against all current rules.

Reprocessing updates lead/account records with new field mappings. Original signal data is never modified.

## Deleting Rules

1. Navigate to **Signal Rules**
2. Click **Delete** on the rule
3. Confirm deletion

> [!WARNING]
> Deletion cannot be undone. Future signals matching the deleted rule will go unprocessed (status: skipped).

Previously processed signals retain their data after rule deletion.

## Troubleshooting

**Changes not taking effect** -- Verify you clicked Save. Changes only apply to signals arriving after the save time.

**Match count changed unexpectedly** -- Review all condition modifications, especially AND vs. OR logic changes.

**Reprocessing not completing** -- Check Signal Explorer for job status. Archived signals cannot be reprocessed.

## Role Attribution

Each signal rule carries a **Buying-group role points** section — one collapsible panel per ICP, each with a point input for every role in that ICP. Expand a panel to see or change how much this signal contributes to each role. Click **Save** inside the panel to persist your changes; a **Save all (n)** button appears at the top when multiple panels have unsaved edits.

You can also manage attribution across all signals at once from the **Role Attribution** tab in Signal Mapping. See [Role Attribution tab](https://docs.trailspark.ai/signal-management/signal-role-attribution-tab) for the full walkthrough, and [Signal and role attribution](https://docs.trailspark.ai/motions/signal-role-attribution) for the conceptual background.

## Next Steps

- [Role Attribution tab](https://docs.trailspark.ai/signal-management/signal-role-attribution-tab)
- [Signal Explorer](https://docs.trailspark.ai/signal-management/signal-explorer)
- [Creating Signal Mapping Rules](https://docs.trailspark.ai/signal-management/creating-signal-mapping)