platform-metadata-deploy

To validate Salesforce metadata before deployment, run a dry-run validation against the target org using explicit deployment scope like source-dir, metadata, or manifest. This verifies components safely without committing changes to the production environment.

Yes, you can deploy Salesforce Agentforce metadata using sf CLI v2. The deployment orchestrates publishing Agentforce components alongside objects, permissions, Apex, and Flows while maintaining correct dependency ordering.

The best way to orchestrate dependency ordering for Apex and Flows is using deployment orchestration that sequences objects, fields, permission sets, and related dependencies correctly. This ensures validation and deployment succeed without missing dependency failures.

Yes, deploying source-based Salesforce metadata to non-source-tracking orgs requires explicit deployment scope such as source-dir, metadata, or manifest. Without this scope, the sf CLI cannot determine which components to validate or deploy.

Salesforce CI/CD metadata deployments often fail due to incorrect dependency ordering, missing validation steps, or undefined deployment scope. Troubleshoot by running a dry-run validation first and ensuring objects, permissions, Apex, and Flows are sequenced correctly.

To quick deploy after successful validation in Salesforce, use the quick deploy operation to finalize previously validated metadata. This skips redundant checks and pushes the exact validated component set directly to the target org.