InstallHub
Skip Strategy
Skip leaves the existing artifact completely unchanged. The conflicting package artifact is not installed for that specific artifact. All non-conflicting artifacts in the package continue to be installed normally.
When to Use Skip
- Installing a marketplace package where some artifacts have been locally customized and should be preserved
- First-time installation of a package where some artifacts already exist from a previous partial install
- Multi-tenant SaaS deployment where each tenant may have tenant-specific customizations that should not be overridden
- Safe "apply what's new, leave what exists" updates
How Skip Works
When Skip is applied to a conflicting artifact, the import engine:
- Records the conflict in the ConflictReport with resolution = Skip
- Does NOT write any data for this artifact
- Continues installing the remaining non-conflicting artifacts
- Notes the artifact as "skipped" in the import result
The existing artifact in the target tenant is completely untouched.
Impact on Dependent Artifacts
Skipped Artifacts Affect Dependents
If artifact A is skipped and artifact B (being installed) depends on A, the import engine uses the existing A in the target tenant (not the package version) to satisfy B's dependency. This is usually the correct behavior — the existing A is still present and functional.
Skip in Import Result
{
"importId": "imp-f9a2c1e8-...",
"status": "Success",
"artifactsInstalled": 4,
"artifactsSkipped": 1,
"installed": [
{ "type": "EntitySchema", "name": "EmployeeSchema", "action": "Created" },
{ "type": "RuleSet", "name": "ApprovalRules", "action": "Created" },
{ "type": "ThreadDefinition", "name": "ApprovalSubflow", "action": "Created" },
{ "type": "ProcessDefinition", "name": "EmployeeOnboarding", "action": "Created" }
],
"skipped": [
{
"type": "AtlasForm",
"name": "EmployeeForm",
"reason": "Conflict — Skip strategy applied",
"existingVersion": "1.0.0",
"packageVersion": "1.3.0"
}
]
}Checking for Skipped Artifacts
After an import with Skip strategy, review the skipped list to understand what was not installed. If the skipped artifact has a newer version in the package, you may want to manually compare the versions and decide whether to replace it separately.
Skip is Non-Destructive
Skip is the safest conflict strategy — no existing data is modified. It is the recommended default for first-time marketplace package installations.