When an Agent calls the flow TriggerInputSchemaMismatch Error

(1) Share

Report

Posted on by TN-26111958-0

Hi everyone,

I've been trying to create an Agent flow in Copilot Studio, and no matter what I do I can't seem to get this TriggerInputSchemaMismatch error to go away.

I've titled two variables in my agent flow:

input_GUID (String)
input_JSON (String)

and I've tested the flow in Power Automate with the exact data I'm passing from Studio and it's run successfully. However, when I look at my topic YAML in Studio, I see:

    - kind: InvokeFlowAction
      id: invokeFlowAction_2QBFOr
      input:
        binding:
          text: =Text(Coalesce(Global.PRD_GUID,""))
          text_1: =Text(Coalesce(Global.known_prd_json, "{}"))

      output:
        binding:
          output_guid: Topic.prd_guid

For some reason the input binding says "text" & "text_1" instead of "input_GUID" & "input_JSON".

I went back to my flow and looked at the code editor for the input variables vs the output variables:

Input -

Output -

The input schema does not seem to update based on the title I'm providing unlike the output schema, and I'm assuming this is the issue but unsure how to resolve. I've tried recreating the flow, removing and deleting the input action, and various other troubleshooting recommendations online.

What else can I try to resolve?

Any help is greatly appreciated!

Error message I keep receiving for reference:

Error Message: The flow 'Sync_PRD_State_v3' ('acdd826d-f3ca-f011-bbd3-6045bd011157') failed to run with response code 'BadRequest', error code: TriggerInputSchemaMismatch. Error Code: FlowActionBadRequest

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (0)

Sort by

abm abm 32,985 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi

Did you renamed these input names?

Copilot Studio stores the mapping in the topic YAML. When you rename inputs in the flow, Studio does not automatically update the YAML. So the old fields stay forever unless you delete and re-add the action.

Thanks

Was this reply helpful? Yes No
TN-26111958-0 9 on at

Like (0)

Report
Copy link

Link copied!
Hey @abm abm,

I've tried

1. Renaming the input variables in the flow to match the "text" & text_1" mapping in the topic YAML

2. Deleting the action and re-adding the action so that the mapping would update, but regardless of the title I use in the input action in the flow, in Studio the YAML is always "text" & "text_1"

3. Re-creating the flow and adding that as a new node in Studio - unfortunately still shows up as "text" & "text_1"

I also tried editing the YAML to be
- kind: InvokeFlowAction id: invokeFlowAction_2QBFOr input: binding: input_GUID: =Text(Coalesce(Global.PRD_GUID,"")) input_JSON: =Text(Coalesce(Global.known_prd_json, "{}"))

but then the Flow action does not recognize the values being assigned as inputs

Was this reply helpful? Yes No
abm abm 32,985 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi

Thanks for your quick reply. Looks like some caching issue this. Try to create another flow with different input parameter names. Then try to map that and see what it generates? If that works then delete and map your old flow.

Thanks

Was this reply helpful? Yes No
TN-26111958-0 9 on at

Like (0)

Report
Copy link

Link copied!
Hi @abm abm I recreated a new flow with different input names, but am still running into the InputSchema error

Update -

I was able to get the flow to work by removing

Text(Coalesce(Global.PRD_GUID,""))

and replacing with

Global.PRD_GUID

& instead of initializing the variable in Studio with
Blank()

I'm using

""

Was this reply helpful? Yes No
Suggested answer

abm abm 32,985 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi

I have tested this and I can see it only add the title which you can refer in your flow with those names but underneath the schema is text and text1 accordingly.

"schema": {

            "type": "object",

            "properties": {

                "text": {

                    "title": "a",

                    "type": "string",

                    "x-ms-dynamically-added": true,

                    "description": "Please enter your input",

                    "x-ms-content-hint": "TEXT"

                },

                "text_1": {

                    "title": "b",

                    "type": "string",

                    "x-ms-dynamically-added": true,

                    "description": "Please enter your input",

                    "x-ms-content-hint": "TEXT"

                }

            },

This is by design and there are no workaround for this. In these situations I generally document the flow steps to mention about these for further maintenance and support.

Thanks

1 people found this reply helpful.

Was this reply helpful? Yes No