Salesforce Decode
Salesforcedecode
Back to questions
AgentforceAdvanceddevopscicdmetadataenvironments

Plan CI/CD and environment promotion for Agentforce configurations

Real World Scenario

Your team manages agents across dev, QA, UAT, and prod orgs. Admins edit topics in prod hotfixes while developers deploy actions via Copado. Config drift is causing QA to no longer represent production.

Expected Answer

• Identify source-of-truth metadata: agent definitions, topics, actions, prompts, and connected knowledge • Establish promotion pipeline with automated retrieval tests and golden conversation regression suites • Separate prompt/action development from knowledge content updates with different approval paths • Use scratch orgs or dedicated Agentforce sandboxes with seeded test data profiles • Implement feature flags or inactive agent versions for canary releases • Document rollback procedures including prior prompt versions and action bindings • Align admin hotfix process with back-merge to Git within 24 hours to stop drift

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Direct answer: Identify source-of-truth metadata: agent definitions, topics, actions, prompts, and connected knowledge Also consider: Establish promotion pipeline with automated retrieval tests and golden conversation regression suites In practice: Separate prompt/action development from knowledge content updates with different approval paths Optimize for scale and operational observability.

Architect Perspective

Agentforce configs are code-adjacent—they need the same discipline as Apex. Prompt changes are production changes. Without automated conversation regression, you will ship silent quality regressions that containment dashboards hide for weeks.