I have a workflow where a Compound Action presents a button to the user. Clicking this button triggers a Conversational Process via a Data Mapper payload. Inside this process, the bot asks the user for an input (e.g., a description or amount_to_add slot) and eventually reaches an HTTP action with a Consent card.
The Issue:
If the user decides to cancel at the consent step (by clicking a Cancel button or typing “cancel”), the flow ends. However, if they scroll up and click the original button to restart the process, the bot remembers their previous answer due to session caching and skips asking the question again.
What I’ve Tried:
To force the bot to start fresh, I tried passing an empty value for the slot directly from the trigger’s Data Mapper, but ran into blockers:
- Passing
nullunquoted resulted in an “Invalid Data Mapper” YAML schema error. - Passing
“null”or an empty string“‘’”allowed the Data Mapper to save, but clicking the button resulted in a generic error in Slack with zero execution logs in Agent Studio. This seems to be because the Orchestrator blocks the request pre-execution due to strict type validation or Required Input Argument constraints on the slot.
My Question:
Is there a supported way to pass a true null or empty value from a Data Mapper to flush a slot’s cache without failing type validation? Alternatively, what is the best practice for ensuring a Conversational Process completely forgets previous slot inputs when re-triggered by a button?
