Common categories
| Category | What it means | Safe next step |
|---|---|---|
| Missing ZIP | The standard company ZIP is blank. | Correct HubSpot, resync, and simulate again. |
| Invalid ZIP | The value cannot be treated as exact ZIP5 or ZIP+4. | Correct the source; TerritoryLogic will not pad or infer it. |
| Unsupported country | The company is recognized as outside the current U.S. program boundary. | Exclude it from this early-access test. |
| Unassigned ZIP | The ZIP is valid but belongs to no territory in the saved draft. | Add the exact ZIP to one territory and run a new simulation. |
| Locked | A manual assignment lock protects the current owner. | Confirm the business reason before an authorized user unlocks it. |
| Inactive or invalid owner | The configured HubSpot owner cannot safely receive the record. | Choose an active owner and save a new draft. |
| Plan limit | The company is newly eligible beyond the workspace record limit. | Reduce scope or wait for paid plans; existing managed records remain preserved. |
| Write failure or changed input | The provider failed, or HubSpot changed after preview. | Inspect evidence; never blindly retry an individual write. |
Use the workbench
- Open Exception workbench.
- Filter by category, program, record ID, or exact ZIP evidence.
- Read the timestamp and last decision reason. The workbench is evidence; it does not expose raw addresses.
- Correct source CRM data or the saved draft, as appropriate.
- 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 company's ZIP, activate an owner only to satisfy a test, or remove a deliberate lock without the record owner's approval. 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, company 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.