Solved: Is servicecallout.requesturi set every time Servic... - Page 2

sgilson · 05-11-2015 01:05 PM

In the dump of my trace session for an API proxy that uses ServiceCallout, I see the variable "servicecallout.requesturi"being set. But that poperty is not listed in the doc.

Is it set on every execution of the Service Callout policy?

Thanks,

Stephen

<VariableAccess>
  <Set success="true"value="/api/geocode/json?address=08008&region=us&sensor=false"name="servicecallout.requesturi"/>

  <Set success="true"value="http://maps.googleapis.commaps/api/geocode/json"name="servicecallout.ExecuteGeocodingRequest.target.url"/>

</VariableAccess>

sarthak

Yes, As far as my knowledge goes this variable is set after the execution of the Service Callout policy . So yes it should be set after every service callout execution.

View solution in original post

santosh_ghalsas

Do we have any impact of this variable on multiple service callout policies getting called in a flow?

I have 3 service callout policies where in third policy is failing to execute and in the trace of that policy the servicecallout.requesturi variable has got the request uri of first service callout policy appended at the end of its own requesturi.

I am not sure why it is not working all of a sudden since the last two service callouts were working fine and then I added first one later.

Do we have any provision to remove this flow variable value?

Thanks,

Santosh

View solution in original post

Is servicecallout.requesturi set every time ServiceCallout runs?