Resource Pack problems

Resource Pack problems are usually visible during review or on the Pack Deployment progress screen. Start with the status shown there rather than deleting the pack or its Resources.

Review reports a conflict

Open the affected Resource and choose whether the site’s local version or the incoming pack version should be used. Continue only when every conflict has a deliberate result.

Installation stays queued

Open System → Site Health → Diagnostics. If Diagnostics reports a background-processing or hosting problem, correct that condition first.

If the Pack Deployment page offers a retry action, use it after the hosting problem has been corrected. It retries the existing queued installation rather than creating another copy of it.

Resource Dependencies

If Site Health reports a Resource Dependency problem, open the Diagnostics tab to see the referencing Resource and missing target. Use Repair Dependencies when it is offered for stale deterministic metadata. A genuinely missing Resource still requires restoring, replacing or removing the broken reference.

Installation is running slowly

Use the stage, item count and Last activity shown on the progress screen. Some stages cannot provide a meaningful percentage. Leaving or refreshing the page does not stop background deployment work.

Installation fails

Read the visible operation result and Site Health report. Resolve trust, dependency, storage or hosting errors before attempting another review or install.

After a failed installation

Use the recovery and retry actions offered by Micro CMS. Avoid manually deleting individual Resources unless a documented recovery procedure specifically requires it.