What is the reason for this?

A customer sets up two LWC OmniScripts, one embedded into another. AccountId is set in a Set Values element in the parent OmniScript. The Accountid set in the parent OmniScript is used to set another Set values element ContextAccountId in the emvedded OmniScript. The embedded OmniScript is activated.

While previewing the OmniScript flow from the parent, it is found that Account I set correct in the parent OmniScript. However ContextAccount in the embedded OmniScript is not set with the Accountid from parent OmniScript. On previewing the embedded OmniScript individually. It is found that ContextAccountId is set correctly.

What is the reason for this? Refer to the exhibit below.

A . The WLC PubSub Messge flag in the Set Values action of the parent OmniScript has not been set.
B . The flag passData.JSON in the parent OmniScript in not configured correctly.
C . A developer failed to include a Navigate Action Element to pass data from the parent OmniScript.
D . Both parent and embedded OmniScripts have the same element name for the Set
Values element.

Answer: A