umbraco-deploy-facts

Diagnose and remediate Umbraco Deploy schema drift between .uda artifacts and environment databases.

Updated May 26, 2026
One-click install
npx skills add https://github.com/robot-denny/ai-sketchlab --skill umbraco-deploy-facts-robot-denny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-deploy-facts
Source: https://github.com/robot-denny/ai-sketchlab/tree/main/.agents/skills/umbraco-deploy-facts
Command: npx skills add https://github.com/robot-denny/ai-sketchlab --skill umbraco-deploy-facts-robot-denny

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Umbraco Deploy environments drift apart silently: the dashboard reports pending or mismatched schema entries that never clear, the bulk import button reports success without importing anything, and restarts or empty commits change nothing. This Skill records the verified mechanics of how .uda artifacts are written and read, why drift happens, and which remediation paths actually work. ## Core Features & Use Cases - Artifact mechanics reference: Explains how Umbraco re-serializes .uda files on startup, how compositions carry hidden properties, and how to parse tab/group structure when diffing artifacts. - Drift diagnosis: Covers the four ways local files and environment databases diverge, including built-in entities never extracted and Cloud auto-commits of re-serialized artifacts. - Remediation runbook: Provides three ordered paths — per-row "Update item" for mismatch states, the Deploy management API (POST /schema/item?udi=...) for pending states, and restart-plus-empty-commit as a last resort — plus what not to waste time on. - Use Case: A content transfer fails with DeploySchemaMismatchException. Instead of restarting the portal, you toggle "hide up to date" in the Deploy dashboard, use the per-row Update item action, and the transfer succeeds in under a minute. ## Quick Start Ask the assistant to diagnose why the Umbraco Deploy dashboard shows pending schema entries that will not clear after a portal restart.

Frequently Asked Questions about umbraco-deploy-facts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix pending schema entries in the Umbraco Deploy dashboard?

Import a single pending artifact via POST /umbraco/deploy/management/api/v1/schema/item?udi={udi} with an OAuth bearer token. One call typically unblocks Deploy's evaluation of the whole pending set, dropping drift to zero without scripting a loop over every entry.

Why does the Umbraco Deploy "Update Umbraco Schema from data files" button not import anything?

The bulk button only refreshes the comparison view on Umbraco Cloud and reports "operation completed" without importing. The control that actually imports file to database is the per-row "Update item" action, visible only for mismatch rows with "hide up to date" toggled on.

Why does an Umbraco Cloud portal restart not re-trigger schema import?

The Deploy bootstrapper compares marker files under the Deploy directory, not .uda modification times, so a restart changes nothing. The startup log shows "Skipping Umbraco content and/or schema import at startup" when this happens.

Why do .uda files show uncommitted changes after running Umbraco locally?

Umbraco re-serializes .uda artifacts from the local database's signatures on every local run, producing churn that looks like an intended schema change. Discard these changes by default and only commit when a type was deliberately edited in the backoffice.

Does Umbraco Deploy remediation differ between Cloud and self-hosted installs?

The artifact mechanics apply wherever Deploy runs, but the dashboard behaviors, bootstrapper, and build-pipeline facts are Cloud-specific. Self-hosted licensees should treat Cloud-marked facts as illustrations of the same reconciliation model, verified against Umbraco 17.x.

What causes DeploySchemaMismatchException during Umbraco content transfers?

The exception occurs at the "Review manifest on target" step when schema signatures diverge between environments. Resolve it by importing the mismatched artifact via the per-row Update item action or the schema/item API endpoint, then retry the transfer.