---
title: "Troubleshoot: Accidental account reassignment"
slug: "troubleshoot-accidental-account-reassignment"
description: "Troubleshoot when accounts are accidentally reassigned to the unassigned node or another territory."
tags: ["Account Reassignment", "Unassigned Node"]
updated: 2026-03-26T21:36:44Z
published: 2026-03-26T21:36:44Z
---

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

# Troubleshoot: Accidental account reassignment

If you accidentally pushed accounts to the Unassigned node or the wrong territory, complete the following process:

1. **Stop all commits:**Do not commit any additional changes until the accounts are accounted for. You want to avoid compounding the error.
2. **Identify gaps:**Use your account history reports in Salesforce (or any backup logs you pulled) to identify the specific list of accounts that were shifted into the incorrect node.
3. **Isolate impacted accounts:** Ensure you have the specific record IDs of the impacted accounts.
4. **Re-run rules on the Unassigned node:** If the accounts are currently in unassigned, trigger the rule engine specifically on that node. This checks the rules against your current, corrected hierarchy rather than the previous (erroneous) commit.
5. **Manually re-assign accounts:** If the re-run doesn't catch impacted accounts, manually move the accounts into the correct target node within the Smart Plan interface before you commit again.
6. **Check the commit preview:** Before you commit, review the change log. Ensure the **Action** column shows the accounts moving to the intended owner, not the previous incorrect owner.

> [!NOTE]
> Note
> 
> If you are unable to recover the data contact your CSM to help you restore the previous account ownership state.