Hi Community
We are building a headless business process which is integrated with the web layer via an API connect layer. The API Connect layer exposes customized APIs which in the backend call the BPM system, task and process APIs.
At certain time, the API layer does an orchestration of the calls to multiple BPM APIs as a business action such as completing a task and fetching the information from the next task. We are observing that the first call succeeds in the orchestration whereas the second call usually throws an error in the first attempt and then succeeds on retry.
Our inference is that the API layer is faster than the speed at which BPM moves the process from one task to another. We are considering putting a delay in between the two calls in the API layer in order to prevent the failure however its not an approach that we like.
I wonder how others are solving this problem. Awaiting to hear from you guys.
Regards
Vaibhav Mehra
------------------------------
Vaibhav Mehra
------------------------------