Set Host URL policy template not replacing the request URL

(1) Share

Report

Posted on by rohitsbots

280

I am passing host url dynamically to custom connector action using Set Host URL policy template but not working. I used headers('containername') in the policy template but I'm getting error that the containername was not sent in headers.

Categories:

Connector development

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Michael E. Gernaey 53,974 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hello @rohitsbots

To quote my 2nd grade teacher lol, "show your work", at least I am pretty sure she said that.. that or, don't bring peanuts to class anymore, probably that too :-)

But in all seriousness, please share your work, versus just sort of explaining it and mentioning an error, that is also not shared.

Cheers and good luck!!

Was this reply helpful? Yes No
CU21030433-0 10 on at

Like (1)

Report
Copy link

Link copied!

Since OP hasn't responded yet and I am getting the same error while trying to use Set host URL policy, I'll share what I have:

1. A header parameter called "new_url" in the Action Definition

2. A Set host URL policy applied to all actions that sets the URL from that parameter

3. Populating the parameter in my flow prior for the action

The error I get when I Test (similar error when I try to use query parameter as well):

{
"error": {
"code": 500,
"message": "Property with name new_url is not present in headers.",
"source": "unitedstates-002.azure-apim.net",
"path": "",
"policyId": "",
"clientRequestId": "",
"dreeSet": "true"
}
}

When I try to use it in a flow, it simply hangs and times out.

Was this reply helpful? Yes No
CU21030433-0 10 on at

Like (1)

Report
Copy link

Link copied!

Oops, accidentally posted trying to upload some screenshots to my previous post. Hope this helps.

Screenshot 2025-0...
Screenshot 2025-0...
Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Was this reply helpful? Yes No
BANDOVS 4 on at

Like (0)

Report
Copy link

Link copied!

I am having this same problem. The strange thing is that the policy is working on old connectors but if I try to create a new one I get the "[variable] is not present in headers error". I'm pretty sure this is a bug.

After messing around with this for a while I found that changing the policy from using the headers('[variable]') to queryParameters('[variable]') works.

(And also updating the header variable to a query variable in the Swagger editor.)

Whilst this is an effective workaround it's a pain because I use these connectors on all new environments and don't want to have to manually update the policy and variable type in each one. I know I could do this at source, but I'm not sure how this effects existing flows that use the connector.

Was this reply helpful? Yes No
CU21030433-0 10 on at

Like (0)

Report
Copy link

Link copied!

Thanks for sharing your experience. Unfortunately, I get the same "not found" error using the query parameters as well!

Was this reply helpful? Yes No
Suggested answer

GV-22041444-0 2 on at

Like (0)

Report
Copy link

Link copied!

we did encounter the same issue.. not sure why this happened, it was working before. Now we changed from headers to queryParameters and it started to work.

Was this reply helpful? Yes No