It appears as of yesterday or today that Post Client Flow execution of Service Callouts is running Async even with a <Response> element as part of the policy configuration.
Definition of the policy:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ServiceCallout async="false" continueOnError="false" enabled="true" name="SC-***-async-external-api">
<DisplayName>SC-***-async-external-api</DisplayName>
<Properties/>
<Request clearPayload="true" variable="sc.request"/>
<Response>sc.response</Response>
<HTTPTargetConnection>
<Properties/>
<URL>https://{hostname}/{api}</URL>
</HTTPTargetConnection>
</ServiceCallout>
Output from Debug Trace:
This runs as part of a Post Client Flow and has been working fine up until maybe yesterday 4/4/2024. Looking at the Apigee Release notes on March 29th there is this note in the Fixed Bugs:
237656263 | Resolved issue with async mode in the ServiceCallout policy when the <Response> element is removed. |
But this appears to either have broken it more, or not completely fixed the issue. Any help here would be greatly appreciated.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |