Diagnose OmniStudio Component Errors

1. Starts from the visible symptom: a blank field on a setup page, missing buttons in an OmniScript, or a deployment error.
2. Reads the component metadata and compares it with the expected structure or template.
3. Checks whether the referenced components exist in the org at all. In one case the FlexCard a page pointed to had no metadata in the org.
4. Names the root cause. Examples include wrong letter case in a configuration name and a missing embedded element.
5. Applies the fix and redeploys when it can be done through metadata.
6. When the fix needs browser-based Setup steps, lists the remaining work and pauses.

Next: Build OmniStudio Components or Deploy OmniStudio Processes.