data360-orchestrate

To troubleshoot Data Cloud pipelines, this skill classifies your org readiness and applies phase-aware read-only verification across ingestion, mapping, identity resolution, segmentation, and activation to pinpoint failure sources before any mutation.

Orchestrating Data Cloud workflows requires connecting cross-phase tasks from connect and prepare to harmonize, segment, act, and retrieve, using data spaces and reusable JSON templates to standardize setup and validation.

Yes, you need the external sf data360 CLI runtime installed alongside git, node, yarn, and npx dependencies, plus a Data Cloud-enabled org to execute phase-aware checks and orchestrate data kits.

Identity resolution and segmentation failures often stem from unclear phase configuration; this skill assesses readiness, classifies the exact setup path, and recommends the next safe step to resolve cross-phase pipeline issues.

Yes, the skill performs targeted read-only checks and plugin verification to diagnose whether a customer 360 issue belongs in ingestion, mapping, identity resolution, segmentation, or activation without mutating your org.

Automated orchestration should not bypass phase-aware verification when a Data Cloud org lacks readiness or when cross-phase failure sources are unclassified, as unverified mutations during pipeline setup can corrupt data spaces.