The administrator at cloud kicks is trying to debug a screen flow that create contacts. One of the variables in the flow is missing on the debug screen. What could cause this issue?

Question

Options

• AThe available for input checkbox was unchecked.
• BThe flow is an inactive version
• CThe field type is unsupported by debugging.
• DThe available for output checkbox was unchecked.

• A
  3% (1)
• B
  3% (1)
• C
  88% (29)
• D
  6% (2)

Explanation

Option C is correct because Salesforce's Flow Debugger does not support all variable data types. When a variable uses an unsupported type (such as certain Apex-defined types or complex object types), it will simply not render on the debug screen regardless of how the variable is otherwise configured - this is a platform limitation, not a settings issue.

Why the distractors are wrong:

• A (Available for Input unchecked): This checkbox controls whether external callers can pass values into the flow at runtime; it's an intentional design choice, not a cause of unexpected missing variables in the debugger.
• B (Inactive version): Salesforce allows you to debug both active and inactive flow versions, so version status doesn't cause variables to disappear.
• D (Available for Output unchecked): This setting controls whether a variable's value can be read after the flow finishes; it has no effect on what appears on the debug input screen.

Memory tip: Associate "missing in debugger" with TYPE, not settings. If your variable is configured correctly but still absent, think "the debugger can't handle this TYPE" - C stands for Complex/unsupported Category of data type.

No community discussion yet for this question.