Run a simulation
- Finish the initial sync and save the current program draft.
- Resolve invalid owner or territory configuration errors.
- Select Simulate. The server captures the revision, draft hash, routing context, and managed-company snapshot.
- Wait for the durable job to finish; reopening the page does not require a duplicate run.
- Inspect categories and record-level reasons before doing anything else.
A simulation expires after 60 minutes. Editing the draft, changing relevant routing context, or materially changing the record snapshot makes its evidence stale.
Read the impact categories
| Category | Meaning | Write implication |
|---|---|---|
| Unchanged | The current owner already matches the decision. | No change needed. |
| Newly assigned | The owner is empty and a valid territory owner was found. | Eligible only under Fill empty or Enforce when writes are authorized. |
| Reassigned | A different valid owner is desired. | Eligible only under Enforce when writes are authorized. |
| Outside / unassigned ZIP | No saved territory owns the exact ZIP. | Preserve the current owner. |
| Locked or unsafe | A lock, invalid owner, invalid location, plan limit, or other guard applies. | Preserve the current owner. |
Enforcement modes
- Recommend: publish decisions and evidence without changing HubSpot ownership.
- Fill empty: write only when the company owner is still blank at the final re-read.
- Enforce: write the calculated owner only when every final safety check passes.
Prepare and execute publication
Only an Account Owner or Admin/Publisher can prepare publication. The preview binds to the exact successful simulation and shows the plan hash, drift allowance, write gate, eligible changes, and safe skips. If more than the smaller of 100 records or one percent changed, run a new simulation. Records inside that allowance are still re-read before a possible write.
- Select Review publish once.
- Confirm the enforcement mode and that the write gate says exactly what you intend.
- If the gate says live writes disabled, publication cannot change HubSpot.
- For an explicitly authorized portal, confirm execution once and monitor processed, succeeded, recovered, skipped, and failed counts.
- If a response is lost, use the product's recovery action. Do not construct a second plan or manually replay individual records.
Guarded rollback
Rollback starts with a compare-only preview of successful TerritoryLogic writes from the current publication. A value is restorable only when HubSpot still contains TerritoryLogic's exact last value and that write is still its latest successful write for the record/property. Later human, integration, or TerritoryLogic changes are skipped.
Rollback execution pauses the program. After a partial rollback, leave it paused, inspect the skipped records in Activity and Exceptions, then build and simulate the desired forward configuration.