Refresh contract
A successful import refreshes the configured connection, not the provider’s whole enterprise. Preview is non-mutating and import performs another read, so results may differ. Validate the returned scope, supported types and completeness before replacing presence state. No adapter invokes or modifies an agent.
Expected outcomes
| Event | Result and operator action |
|---|---|
| Display name changes, stable source ID | Update the observation; preserve its binding and business decisions. |
| New source ID | Create distinct evidence. Review continuity; do not silently transfer an older decision. |
| Incomplete pages, timeout or provider error | Keep earlier evidence; show source error/staleness. Repair scope or credentials and retry. |
| Missing record in a complete successful read | Preserve history and mark not observed according to that adapter’s contract. |
| Paused connection | Retain evidence; mark unavailable for guided linking. |
| Helix record absent from an offset scan | Conservative stale prior evidence; offset scans do not prove deletion. |
Freshness is not runtime health
Guided linking requires enabled, healthy source reads with present/non-stale evidence and a valid timezone-aware last-seen timestamp. This is an availability gate. It does not establish that the agent is executing, that a deployment is healthy, or that an age-based SLA was met.
Troubleshooting sequence
- Confirm the selected workspace and connection scope.
- Read the source status and last-success time separately from the business lifecycle.
- Ask the source administrator to verify read permissions and exact resource scope.
- Preview again before importing a corrected inventory.
- Inspect the preserved source IDs and owner decisions after refresh.
- Do not delete old observations merely to make counts look clean.