web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Up Program - Microsoft Copilot Studio Exp...
Suggested Answer

Still getting “TriggerInputSchemaMismatch” even though all fields match

(3) ShareShare
ReportReport
Posted on by 21 Power Up Champ - 2025

Hi everyone,

I'm trying to build an Employee Onboarding Copilot that schedules Teams meetings for new hires using Power Automate. My flow trigger is set to “When an agent calls the flow,” and I’ve defined the following input parameters:

 

  • EmailAddress (String)

  • StartTime (String)

  • EndTime (String)

  • TrainingTitle (String



  •  

In Copilot Studio, I’m calling the flow using these exact fields. The values passed look like this:

 
 
json
{
"EmailAddress": "michaelkeimeyer@2xgr35.onmicrosoft.com",
"StartTime": "2025-06-16T14:00:00Z",
"EndTime": "2025-06-16T16:00:00Z",
"TrainingTitle": "Introduction to IT Systems"
}

However, I keep getting this error:

 

The flow failed to run with response code 'BadRequest', error code: TriggerInputSchemaMismatch.

FlowActionBadRequest – even though the structure seems correct.


I've checked:

 

  • The input field names in the trigger exactly match what Copilot is sending

  • The Flow is saved and published

  • I’ve re-added the action in Copilot multiple times to refresh the schem

What else can cause this mismatch? Is it possible that Copilot is still referencing an old version of the flow? Or is there some hidden issue with how the agent sends data?

 

Thanks in advance for any help!

– Michael

Categories:
I have the same question (0)
  • Suggested answer
    Michael E. Gernaey Profile Picture
    52,569 Super User 2025 Season 2 on at
    Still getting “TriggerInputSchemaMismatch” even though all fields match
     
    Just a couple of things
     
    1. Can you share the Flow itself ( really just trigger picture )
    2. is the flow a CoPilot flow or a Flow Flow (meaning not generated specifically as a CoPilot Flow, just generated as an Action AKA standard Flow UI)
     
    3. Just for kicks... can you create another Flow.
    In that Flow call your Schedule Flow
    pass in the same values
    See if it works
     
    Because if it works then its CoPilot
    If it fails, then delete the trigger and re-add it
     
    Also, is this all in a solution? When is the last time you published all customizations?
  • MK-11062352-0 Profile Picture
    21 Power Up Champ - 2025 on at
    Still getting “TriggerInputSchemaMismatch” even though all fields match
    Hi, 
    here the sceenshots: 
    1. Screenshot: Sure! I’ll attach the trigger screenshot shortly.

    2. Type of Flow: It is a CoPilot Flow – the trigger was created as part of the CoPilot tool using the TaskDialog structure.

    3. New Flow Test: I’ll try your suggestion and create a new standard Flow that simply calls the existing Schedule Flow with the same values. That’s a great idea to isolate whether it’s a CoPilot-specific issue or not

    Also:


    • Yes, everything is part of a solution.

    • I’ve published all customizations – the last time was [insert date/time or say "just now"].

    • I recently updated the propertyName fields to be more readable (e.g. EmailAddress, StartTime, etc.), so maybe the Flow is still expecting the older names like text, text_1...

    Next steps:


    • I’ll test with a new Flow and see if that resolves it or confirms the source of the issue.

    • If needed, I’ll re-add the trigger as you suggested.

    •  

    Thanks again – I’ll report back shortly!

     
  • Suggested answer
    Michael E. Gernaey Profile Picture
    52,569 Super User 2025 Season 2 on at
    Still getting “TriggerInputSchemaMismatch” even though all fields match
     
    So to clarify something. When you say rename, yeah.. there are definitely times the metadata gets stucks. Thats why I usually delete the trigger itself and re-add to do that. Plus, if you are in CoPilot and click the edit in Power Apps, but make certain changes... they aren't handled well because you are technically disconnected, but connected so CoPilot doesn't want you to really treat it like its a stand alone. Man I am explaining this poorly I think.
     
    But personally I would recreate the Flow.
  • LA-24071600-0 Profile Picture
    6 on at
    Still getting “TriggerInputSchemaMismatch” even though all fields match
    Did you manage to figure this out? Getting the exact same error message :( 
  • AM-17061934-0 Profile Picture
    6 on at
    Still getting “TriggerInputSchemaMismatch” even though all fields match
    @LA-24071600-0 check if the ID's of fields in Copilot Studio are the same in Power Automate. I got the same problem and i discover (for some uknown reason) that Copilot (or Power Automate) change the IDs.
     
    For example: 
    I have a client field with id "text_field1" and email field with id "text_field2". Then Copilot try to assign client to text_field2 and email to text_field1, thats why i got TriggerInputSchemaMismatch error.
     
    Hope helps :)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes arriving December 5th!

Important updates for the Power Up Program Community – simplifying the forums…

Chiara Carbone – Community Spotlight

We are honored to recognize Chiara Carbone as our Community Spotlight for November…

Leaderboard > Microsoft Power Up Program Community

#1
timl Profile Picture

timl 437 Super User 2025 Season 2

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 169 Super User 2025 Season 2

#3
mmbr1606 Profile Picture

mmbr1606 109 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics