Post Client Flow Service Callouts running in Async even with <Response> element

Google Cloud Apigee
,
1

It appears as of yesterday or today that Post Client Flow execution of Service Callouts is running Async even with a 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:

jallenfni_0-1712329921756.png
jallenfni_0-1712329921756.png1137Ɨ317 30.2 KB

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 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.

2

Your message was originally posted a long while ago. Iā€™m sorry you were experiencing that problem. I agree with you that the original fix for the bug you cited, 237656263, was incorrect. Since then, Apigee has re-engineered the fix for the bug . This is from the release notes page, updated last week:

dchiesa1_0-1734457470548.png
dchiesa1_0-1734457470548.png1185Ɨ480 50.6 KB

So we think this is now working correctly. Please test again, and advise.

1 Like
3

ā€“ EDIT ā€“
Was able to load up the proxy into an environment and it worked now as I had expected it to.

I will attempt to test it again, we have changed how we are doing things for this customer so may have to recreate a flow that handles this. But I appreciate your response!

1 Like