Hi @TanyaS58: When you say the external system is taking time to respond, can help to understand if this is a async request made to external system (or) live call to get data from external system and what is the delay you are expecting. Also please help us to understand the use case and the usage of data in application.

Based on the application need, please also check if you can cache the data in PEGA using data page (or) a local storage. In this case you can make the data available in your cache (or) local storage using a background process (refreshed periodically based on application need) and your application logics can refer to the local data.

Thanks.

@TanyaS58 if kafka is available, then that would be best approach. Service team just need to publish the data to the topic and you just need to consume the topic and with that data you can proceed the case. 

If kafka is not available, you can have a dedicated queue processor to hit the api and check for the status and data. Till the data is not available you need to retry the api hit, this will be like a loop using decision shape(negative path of decision shape) . Once data is available and status code is 200, you can proceed the flow which will be the positive path through the decision shape. 

@TanyaS58  Based on your use case, it needs to be asynchronous call to external system.

Pega Provides various asynchronous communication types like

• Listeners
• Files
• REST

You can use any of these based on your enterprise Architecture.

@TanyaS58

It is important to identify the root cause of the issue. Check Pega Logs and Review External System Performance

Regards,

Mamatha Adiraju

@TanyaS58

Please check below topic to understand, commonly-used approaches for asynchronous integration

https://academy.pega.com/topic/asynchronous-integration/v2/in/46336/46331