Hi Team,
I’m seeing what looks like a bug with the Agent chat trigger / Input form configuration.
Context
- Agent type: interactive, using a Chat Message trigger with an attached Input form
- Input form fields: configured as Multiple choice (with defined option lists)
Expected behavior
- When I edit and republish the workflow (even if I only change downstream steps), the trigger’s Input form field types should stay Multiple choice, unless I explicitly change them.
Actual behavior
- After every workflow update/publish, all Input form fields on the chat trigger are silently reset to Text type.
- This happens regardless of what I changed in the workflow (even when I don’t touch the trigger at all).
- I have also tried explicitly telling the agent (via the natural-language builder panel) not to modify the chat trigger, but the fields are still reset to Text after publishing.
Why I think this is a platform issue (not my agent logic)
- Glean docs for Input form triggers say fields can be Text, Document, or Multiple choice, and they don’t mention any automatic coercion back to Text when a workflow is edited or republished.
- Chat Message and Input Form triggers are documented as separate trigger types; chat triggers can surface form-style inputs via placeholders, but there’s no documented behavior that would downgrade previously configured Multiple choice fields to Text on update.
- I can’t find any release notes or documentation that describe this “reset to Text on publish” behavior as expected.
Repro steps
- Create an agent with a Chat Message trigger.
- Add an Input form to the trigger; configure one or more fields as Multiple choice with options.
- Add a few normal steps to the workflow.
- Publish the agent.
- Re-open the agent, make a small change in any downstream step (not in the trigger), and publish again.
- Open the chat trigger configuration and observe that all Input form fields have reverted to Text type.
Questions / request
- Is this a known issue with chat-trigger Input forms?
- Is there any current workaround to keep the field types as Multiple choice across workflow edits/publishes?
- If this is unintended, could this be logged as a bug/defect for the Agent Builder so Multiple choice configurations persist correctly?
Regards,
Sultan Shahabuddin
CSGi
