Asynchronous calls using service callout policy in Apigeex

[nagesh_k]

Is there a way to implement asynchronous  calls using service callout policy in ApigeeX.

If not then what are the best possible ways to implement same in ApigeeX using endpoint url

Thanks

[AlexET]

Thanks for joining the community @nagesh_k and sharing your question - We’re monitoring this thread to help ensure it gets answered, and we invite other members to pitch in as well.

Don’t forget to explore our events and articles for more resources 😊

[dchiesa1]

Is there a way to implement asynchronous  calls using service callout policy in ApigeeX.

yes.  Do not specify the Response element. 

If not then what are the best possible ways to implement same in ApigeeX using endpoint url

There is no way to use "only Apigee" to implement an async fire-and-forget HTTP call, for the target endpoint. For that you would need to plug in something behind Apigee, something like App Integration.  Apigee would call AppInt, AppInt would return immediately ("got your request"), and then asynchronously invoke the desired HTTP Target. 

But you may not need this if you can use ServiceCallout. 

[nagesh_k]

Hi @dchiesa1 

Thanks for the reply

I have tried as you suggested, the proxy call is still waiting for 32 seconds

In service callout i have added postman mock-server url which delays the response for 30 seconds

Below is the url for proxy zip folder

https://drive.google.com/file/d/1pYrsmTTT0gLIVU5NCXW8ZY1awklSagqW/view?usp=sharing 

I might have missed something, please help me in fixing this issue

Thanks

[dchiesa1]

Hi Nagesh

I'm not sure what's going on with your system, but this behavior is working correctly in Apigee X. Here is a screencast that I just recorded showing how it works: https://youtu.be/krLzUw1sAgk

In this sample proxy bundle (attached), I used an API published by "dummyapis.com" , but I also tried the same with the endpoint you used, and of course it worked the same way.  

Looking at your proxy bundle, I think MAYBE you are not deploying  it into Apigee X.  If you are using Apigee Edge, or OPDK, or Apigee hybrid, you don't have this capability.  It will come soon (guessing January?) in hybrid. I am not sure if the engineering  team will release this enhancement in Apigee Edge or OPDK.  I think probably not. 

[nagesh_k]

Hi @dchiesa1 ,

I have checked we are using Apigee X (payas you go) SAAS . 

Its not working for us

Apigee release notes  |  Google Cloud

As per above link , issue is still there in Apigee x. They are yet to fix 

Please check and help us in prioritize the fix for this bug 

Thanks

[dchiesa1]

hmmm, that's frustrating. 

@Veronique do you know? 

[Veronique]

Hi @nagesh_k,

The fix will be in the upcoming release for Apigee X, planned for this week. This will be for all customers including PAYG orgs. Please follow https://cloud.google.com/apigee/docs/release-notes as it will be listed as a fixed issue. Note that it can take a couple days for rollout to your org.

[AlexET]

Hi @nagesh_k, I just wanted to follow up on your question and see if the update mentioned by @Veronique resolved your issue. Let us know if the fix worked or if you need further assistance! 🙂

A big thank you to @dchiesa1 and @Veronique for their insights and support in addressing this thread.