Copilot Studio Agent Flows: Errors, Ownership and Reliable Patterns
Diesen Beitrag auf Deutsch lesen
Practical controls for agent flows covering visibility, 100-second timeouts, schema refreshes, maker credentials, co-ownership and agent handoffs.
TL;DR
Copilot Studio agent flows need the When an agent calls the flow trigger, Respond to the agent action, asynchronous response set to Off, Solution placement and the Copilot Studio plan to appear as tools. Synchronous calls have a 100-second limit, while schema changes require refreshing the flow node.
Original by Petros Feleskouras, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Keep agent flows in a Solution with the required trigger and response action, and refresh the Copilot Studio node after changing parameters so tools remain available and schemas match.
- Admins/CoE: Review flow co-owners and Connection References separately from agent tool credentials, because access and runtime identity are configured in different places.
- Security/Compliance: Use scoped co-ownership and controlled storage links for larger images, since flow access can be granted without exposing the agent and cloud storage enables access control.
Frequently asked questions
Why does my Copilot Studio agent flow not appear as a tool?
The flow needs the When an agent calls the flow trigger, Respond to the agent action, synchronous response mode, Solution placement and the Copilot Studio plan.
How can I avoid the 100-second FlowActionTimedOut error in Copilot Studio?
Respond before 100 seconds, then continue approvals or human input asynchronously and call the agent again with Execute Agent and the Conversation ID.
Where do I set maker credentials for actions inside a Copilot Studio agent flow?
Update each Connection Reference inside Power Automate. The maker credential setting on the agent tool does not change authentication for flow actions.