Copilot Studio

Agent workflow

(0) Share

Report

Posted on by CH-11092301-0

Trigger runs correctly in agent workflow but doesnt invoke first agent

Categories:

Autonomous agents

All responses (4)

Answers (0)

Sort by

Suggested answer

Mohsin Ali 1,075 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @CH-11092301-0 - Can you confirm that all of your agents are in a Published state?
Also, in Copilot Studio, check the Activities tab. That should help you verify whether the user request is actually reaching the agent and, if it is, where the execution is stopping or failing.
If there is no activity recorded at all, then the issue may be happening before the request reaches the agent.
Suggested answer

11manish 4,802 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!
A review of the flow shows that the flow itself may show as successful, while the next actions are not completing properly. This can happen because of expired connection tokens, missing required inputs for the agent, or an old agent/environment reference that is still pointing to an unpublished version.

To fix the issue:

Re-authenticate the connection references used by the Run an agent actions.

Make sure the required values from the email trigger are correctly passed to the first agent.

Select the correct agent again from the dropdown so that the action is linked to the correct environment and published agent version.
Suggested answer

11manish 4,802 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Independent verification of the flow execution behavior reveals that cloud flow triggers can report a successful execution status while downstream actions appear stalled due to underlying connection token timeouts, unmapped required agent input payloads, or stale environment references pointing to unpublished agent versions.

To resolve this issue, re-authenticate the connection references used by the "Run an agent" actions, ensure valid dynamic content fields from the email trigger are properly passed into the first agent's input parameters, and re-select the target agent from the dropdown to bind it to the correct environment ID.
Suggested answer

M Bilal Khan 384 on at

Like
a
(0)

Report
Copy link

Link copied!
Since the trigger is completing successfully but the first Run an agent isn't being invoked, I'd troubleshoot that action separately from the trigger.

A few things to check:

Open the flow run history and expand the first Run an agent action. Check whether it is Skipped, Failed, or never started.

If it's Skipped, check the action's Run after settings and whether there is any condition/branch before it.

If it is Failed, check the exact error returned by the agent action, especially the connection, agent/environment, and permissions.

Open the agent action and re-select the agent. If the agent was renamed, moved, or changed environments, the existing reference can sometimes become invalid.

If the agent is in a solution, verify the solution and connection references are correctly configured in the environment where the flow is running.

Test the same agent directly from Copilot Studio. If it works there but not from Power Automate, the issue is more likely with the flow's agent connection/configuration.

Also check whether the first agent is waiting for an input value. Make sure the dynamic content you're passing from When a new email arrives (V3) is actually populated.

Because the subsequent Run an agent 1/2/3/4 actions are also in the flow, the key question is whether the first agent is being skipped or failing. The run-history details for that first action would usually reveal the cause.

If you can share the error/details shown when you expand Run an agent in the flow run, that would make it much easier to pinpoint.