Service Callout request failing

I have a service callout which is making a call to internal proxy deployed in same org and env.

I am using :

<ServiceCallout name="Token-Callout">
    <DisplayName>Token Callout</DisplayName>
    <Request variable="myRequest">
        <IgnoreUnresolvedVariables>false</IgnoreUnresolvedVariables>
        <Set>
            <Verb>GET</Verb>
        </Set>
    </Request>
    <Response>token_response</Response>
    <LocalTargetConnection>
        <APIProxy>TestProxy</APIProxy>
        <ProxyEndpoint>default</ProxyEndpoint>
    </LocalTargetConnection>
</ServiceCallout>

When i am making the request this service callout is failing with below error :

{"fault":{"faultstring":"Raising fault. Fault name : Raise-Missing-Endpoint-Configuration-Error","detail":{"errorcode":"steps.raisefault.RaiseFault"}}}

Test Proxy is available and deployed in same org and env and has a default Proxy endpoint as well.

Request is not reaching the intended proxy i am not getting any trace in it.

Could some one please help me to identify what is wrong with my configuration?

0 1 305
1 REPLY 1

I can tell from the error message that there is a policy, somewhere in your system, of type RaiseFault, with name "Raise-Missing-Endpoint-Configuration-Error".

I think this policy is explicitly being invoked by logic in one of your proxies.

Can you check for that? Check into Flowhooks too.

It might be helpful to turn on tracing in both API Proxies.

Normally if a fault is raised by the Apigee Edge infrastructure, the fault name will not be "steps.raisefault.RaiseFault" . That fault name is reserved for faults being raised by your proxy logic.