If you accidentally pushed accounts to the Unassigned node or the wrong territory, complete the following process:
Stop all commits: Do not commit any additional changes until the accounts are accounted for. You want to avoid compounding the error.
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.
Isolate impacted accounts: Ensure you have the specific record IDs of the impacted accounts.
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.
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.
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
If you are unable to recover the data contact your CSM to help you restore the previous account ownership state.