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 / Copilot Studio / Agent Published failed !!
Copilot Studio
Suggested Answer

Agent Published failed !!

(0) ShareShare
ReportReport
Posted on by

I am having issue of agent not being published. I have configured a child agent with required inputs in an agent. Previously i was able to publish this kind of configuration. Also the ss below show i can still publish such agents( this one is in different env)

I have the same question (0)
  • Suggested answer
    Sayali-MSFT Profile Picture
    Microsoft Employee on at
    Hello,
    From your screenshots, the publish failure occurs only in the environment where the child agent (FinancingAndAnnexAgent) has a single required input (generalInfo) set to “Dynamically fill with AI”, no explicit parent binding, and no observable output (“Don’t respond” completion). In contrast, publishing succeeds in another environment where multiple required inputs are present and resolvable—even though they are also AI-filled.

    The root cause is a recent, undocumented validation change in Copilot Studio (late Jan / Feb 2026) that introduced stricter publish-time checks for child agents. The platform now performs a static resolvability validation before allowing publish. If a required input is not guaranteed to be resolved at runtime—and the agent produces no observable output—publishing can fail. Previously, a single AI-filled required input was allowed because runtime resolution was trusted; now the system requires clearer guarantees.

    This change was introduced to prevent runtime agent chaining failures and unclear input provenance, especially with autonomous/background agents. The breaking combination in your case is: child agent + required input + AI-filled source + no parent binding + no output. 

    Recommended fixes include:

    1. Add a dummy output (cleanest fix) and respond with it to satisfy validation.
    2. Make the input optional and handle inference in instructions.
    3. Explicitly bind the input from the parent agent.
    4. (Less ideal) Add a second required input.


    This issue appears only in newer or updated environments due to staged rollout of the new validation logic.

    TL;DR: Not a configuration mistake—this is a new publish-time validation rule. The simplest fix is to add an output or change completion behavior so the agent produces observable output

    Reference Document0-
    1.Add a child agent - Microsoft Copilot Studio | Microsoft Learn
    2.Using Inputs and Outputs in Child and Connected Agents | The Custom Engine
    3.Microsoft Copilot Studio troubleshooting | Microsoft Learn

     
     
     

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 277

#2
11manish Profile Picture

11manish 206

#3
sannavajjala87 Profile Picture

sannavajjala87 156 Super User 2026 Season 1

Last 30 days Overall leaderboard