Guide 05

Work with ownership exceptions and safety states

TerritoryLogic preserves unsafe records, but not every preserved state creates a row in the Exception workbench. Use the surface that owns the evidence instead of guessing.

Last reviewed July 29, 2026 · Early-access documentation

What appears in the Exception workbench

The current workbench contains evaluation exceptions and invalid program-configuration evidence. These are the common record-level evaluation categories:

CategoryWhat it meansSafe next step
Missing ZIPThe program's mapped ZIP/postal property is blank and the record has no usable city/state evidence for an explicitly claimed whole-state territory.Correct HubSpot or configure the intended whole-state fallback, then resync and simulate again.
Invalid ZIPThe value cannot be treated as exact ZIP5 or ZIP+4.Correct the source; TerritoryLogic will not pad or infer it.
Unsupported countryThe managed record is recognized as outside the current U.S. program boundary.Exclude it from this early-access test.
Unassigned ZIPThe ZIP is valid but belongs to no territory in the saved draft.Add the exact ZIP to one territory and run a new simulation.
Inactive or invalid ownerThe configured HubSpot owner cannot safely receive the record.Choose an active owner and save a new draft.

Preserved safety states outside the workbench

StateWhere to find it nowSafe next step
Manual lockOpen the latest simulation preview or the TerritoryLogic card on the managed HubSpot record. Lock and unlock actions are also recorded in Activity.Confirm the business reason before an authorized user unlocks it.
Plan limitOpen the simulation's Plan limit category and the Plan-limit queue on the Dashboard.Reduce the program's managed-record scope or wait for an available higher plan. No desired owner or write is produced for a plan-limited record.
Changed input or write resultInspect the publication or rollback progress/result that produced the safe skip or failure. Attempted CRM writes and their terminal results also appear in Activity.Re-simulate changed input. For a failed write, preserve the request evidence and use the displayed recovery action instead of replaying one record manually.

Use the workbench

  1. Open Exception workbench.
  2. Filter evaluation exceptions by category, program, record ID, or exact ZIP evidence.
  3. Read the timestamp and last decision reason. The workbench is evidence; it does not expose raw addresses.
  4. Correct source CRM data or the saved draft, as appropriate.
  5. Run a resync when HubSpot input changed, save when configuration changed, and then simulate again.

When not to “fix” the record

Do not invent a ZIP from city/state, copy a nearby record's ZIP, activate an owner only to satisfy a test, or remove a deliberate lock without the record owner's approval. City/state evidence is not a ZIP: TerritoryLogic uses it only when the mapped ZIP property is truly missing and a territory explicitly claims the whole state. A preserved exception is safer than a confident-looking decision built on false data.

Escalate unexpected changes

If a HubSpot owner changed without an explicitly confirmed, authorized publication, stop testing. Record the portal ID, object type, record ID, approximate time and time zone, and the correlation/request ID shown by TerritoryLogic. Follow the support escalation path without sending credentials or a CRM export.