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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Power automate, the AP...
Power Automate
Suggested Answer

Power automate, the API operation

(0) ShareShare
ReportReport
Posted on by
"Flow save failed with code 'WorkflowOperationParametersExtraParameter' and message 'The API operation does not contain a definition for parameter 'item/source'.'." i am having issue on my powerautomate
Screenshot 2026-03-23 155158.png
I have the same question (0)
  • Suggested answer
    Tharusha Jayadeera Profile Picture
    80 on at
    Hi ,

    You are passing a parameter that does not exist in the connector schema.
     
    This happens when:
    • Action was copied from another flow/environment
    • Connector definition changed (Common with SharePoint / custom connectors)
    • Dynamic content got serialized incorrectly -> item/source instead of valid path
    • Manual JSON edit or import created invalid parameter mapping
     

    If this helped solve your issue, please mark it as ✅ Accepted Answer.
    If you found it useful, a 🩷 Like is always appreciated.

    Thanks,
    Tharusha

  • Suggested answer
    deepakmehta13a Profile Picture
    322 on at

    Hi,

    This error:

    "WorkflowOperationParametersExtraParameter – The API operation does not contain a definition for parameter 'item/source'"

    usually means that one of your actions is referencing an old or invalid parameter that no longer exists in the connector schema.

    A few quick things to check:

    1. Check dynamic content / expressions
      Somewhere in your flow (often inside Apply to each or a custom action), there is likely a reference like:

    • item()?['source']
      or similar

    If the connector/action no longer returns source, the flow fails to save.

    1. Re-select fields instead of typing manually
      Open the failing action:

    • Remove the field/expression

    • Re-add it using dynamic content picker

    This ensures it matches the current schema.

    1. Check renamed or updated actions
      If the flow was:

    • Edited manually in code view

    • Generated by Copilot

    • Or copied from another flow

    Some parameters (like source) may no longer be valid.

    1. Focus on Apply to each
      Since your flow has an Apply to each, check inside it:

    • Any expression using item()

    • Make sure all properties actually exist in the current output

    1. Quick fix (most common)
      Delete and re-add the action that is throwing the error (often resolves schema mismatch issues).

     

    If this gets resolved, it would be great if you could share what worked for you. It will help others in the community who might run into the same issue.

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Hope this helps.

    If this helps resolve your issue, please consider marking the response as Verified so it can help others facing a similar scenario.

    If you found this helpful, you can also click “Yes” on “Was this reply helpful?” or give it a Like.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Vish WR Profile Picture

Vish WR 873

#2
Valantis Profile Picture

Valantis 813

#3
Haque Profile Picture

Haque 526

Last 30 days Overall leaderboard