Power Automate

Recently `When a build completes` always return 256 items for one build completing

(1) Share

Report

Posted on by JZ-09060643-0 Microsoft Employee

It occurs in many of my workflows

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Valantis 6,466 on at

Like (1)

Report
Copy link

Link copied!

Hi @JZ-09060643-0,

This sounds like a connector-level regression rather than a configuration issue. The "When a build completes" trigger returning 256 items for a single build completion across multiple workflows is not expected behavior and not documented as a known limitation.

A few things to check to help narrow it down:

1. Check the raw trigger output in the flow run history. Expand the trigger and look at the body are these 256 items all from the same build, or is the trigger firing once and returning a list, or firing 256 times?

2. Check if this started after a specific date and whether it correlates with any Azure DevOps or Power Platform service update.

3. Check the Azure DevOps service health at https://status.dev.azure.com and the Power Platform service health at admin.powerplatform.microsoft.com for any active connector incidents.

Since you're a Microsoft Employee and it affects many workflows, the fastest path is raising an internal support or engineering escalation rather than going through the community forum. If the trigger is consistently returning 256 items for one event, that's a connector bug that needs the Azure DevOps connector team to investigate.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

11manish 2,993 on at

Like (0)

Report
Copy link

Link copied!
Some Azure DevOps connector actions and triggers have internal limits (commonly 100, 256, 500, etc.). If the trigger payload contains collections such as:

Associated work items

Changesets/commits

Artifacts

Tags

the connector may truncate the data at 256 records. This can appear as though the trigger is returning 256 items for a single build.

Was this reply helpful? Yes No