Answered

Power Automate - AI Builder (Prompt) Issue: Item.item/source

(9) Share

Report

Posted on by OK-12081121-0

Since ~2 days, the AI Builder – Execute prompt (Predict V2) action injects an extra parameter by itself and every run fails. This happens in new flows and existing ones; even the basic preconfigured prompts fail, so it’s not due to my custom mapping.

What gets added automatically

Field shown in the action as item.item/source, value:

In the code view / request payload this becomes a top-level parameter item/source, which OData rejects.

Error

Repro steps

Add AI Builder – Execute prompt (Predict V2) to a flow.
Map only the required inputs (no “source”/telemetry fields).
Save and run.
Open Code view → see item.item/source added automatically.
Action fails with the error above.

Tried

Deleting the field (X) → it reappears on save/run.
Setting the field to null → flow doesnt accept it.
Rebuilding the action & creating a brand-new flow → same result.

Impact

All flows using Execute prompt (Predict V2) are currently blocked.

Categories:

Calling actions from Copilot Studio

I have the same question (39)

All responses (4)

Answers (1)

VS-14081414-0 13 on at

Like (2)

Report

Hi,

did you find a solution. I've got the same problem and I'm stuck with it.

With kind regards.

Vincent.

1 people found this reply helpful.

Was this reply helpful? Yes No
paLuke 18 on at

Like (4)

Report

I experienced the same problem.

As soon as I saved the flow in the Classic designer it started to work again and did not inject an extra item.item/source into the input.

Run a prompt Input when saved in New designer - injects extra item.item/source

"parameters": {

"recordId": "",

"item/requestv2/Document_20input/base64Encoded": "",

"item": {

"item/source": {

"consumptionSource": "",

"partnerSource": "",

"consumptionSourceVersion": "",

"partnerSourceVersion": "",

"displayName": ""

}

},

"item/source": ""

}

Run a prompt Input when saved in Classic designer - has one item/source

"parameters": {

"recordId": "",

"item/requestv2/Document_20input/base64Encoded": "",

"item/source": ""

}

4 people found this reply helpful.

Was this reply helpful? Yes No
Verified answer

OK-12081121-0 45 on at

Like (4)

Report

I spoke with Microsoft Support about this. The only reliable solution was to switch to the classic design (turn off the modern design). After doing so, make sure to save the workflow: this step is crucial. Once saved, it should work; it did for me for the rest of the day. I’ll mark this as the correct answer if it’s still working tomorrow.

7 people found this reply helpful.

Was this reply helpful? Yes No
JL-19081337-0 2 on at

Like (0)

Report

We encountered this error using the New Designer UI - so we switched to the Classic Design mode, but we are still getting a related error: "Flow run timed out". Does anyone have any suggestions here?

Was this reply helpful? Yes No