An Agentforce has created a copilot custom action using flow as the reference action type. However, it is not delivering the expected results to the conversation preview, and therefore needs troubleshooting.
What should the Agentforce Specialist do to identify the root cause of the problem?
A. In Copilot Builder within the Dynamic Panel, turn on dynamic debugging to show the inputs and outputs.
B. Copilot Builder within the Dynamic Panel, confirm selected action and observe the values in Input and Output sections.
C. In Copilot Builder, verify the utterance entered by the user and review session event logs for debug information.
A. In Copilot Builder within the Dynamic Panel, turn on dynamic debugging to show the inputs and outputs.
Explanation
When troubleshooting a copilot custom action using flow as the reference action type, enabling dynamic debugging within Copilot Builder's Dynamic Panel is the most effective way to identify the root cause. By turning on dynamic debugging, the Agentforce Specialist can see detailed logs showing both the inputs and outputs of the flow, which helps identify where the action might be failing or not delivering the expected results.
Option B, confirming selected actions and observing the Input and Output sections, is useful for monitoring flow configuration but does not provide the deep diagnostic details available with dynamic debugging.
Option C, verifying the user utterance and reviewing session event logs, could provide helpful context, but dynamic debugging is the primary tool for identifying issues with inputs and outputs in real time.