An administrator at Universal Containers has successfully deployed a new agent from a sandbox to production using a change set. The agent uses a prompt template that invokes a Salesforce flow to perfo

Question

Options

• AThe flow was not manually activated in the production org after the deployment.
• BThe user in production does not have permission to run the flow.
• CThe change set did not include the dependent Apex classes for the flow.

• A
  75% (24)
• B
  16% (5)
• C
  9% (3)

Explanation

This is one of the most common post-deployment issues in Salesforce: when a Flow is included in a change set and deployed to production, it arrives in an inactive (Draft) state by default. The administrator must manually navigate to the Flow in Setup and activate it in the production org. Since the flow is confirmed to be present but fails at runtime, inactive status is the most likely cause. Option B (permissions) is possible but would typically produce an access/authorization error rather than a generic failure, and is less common. Option C is less likely because if dependent Apex classes were missing, the change set deployment itself would have failed or the flow would not have been created successfully.

No community discussion yet for this question.