'x-api-key' stop working from in HTTP Request trigger Header

(0) Share

Report

Posted on by Khurshid Wali

I have a flow which stopped working recently (13 Nov on the UAT Flow) and (15 Nov on the Prod flow). After debugging, I found out that the Power Automate trigger is skipping the x-api-key on the header. When I change the x-api-key to x-api-key2, it starts appearing on the flow header. I want to know if it is now a reserved keyword, that Power Automate trigger is skipping 'x-api-key'.

Kindly share your thought if there is any change, or same happen to anyone recently.

Categories:

Business Process Flows

I have the same question (0)

All responses (1)

Answers (0)

developerAJ 4,598 on at

Like (0)

Report

'x-api-key' stop working from in HTTP Request trigger Header

if you can help us with the screenshots of the flow that will be helpful

trigger does have inbuilt properties which you can refer from the flow history

Was this reply helpful? Yes No