Hi,
We have a simple workflow with 2 activities
1. Call another microservice to fetch data based on the input
2. Post this data on a webhook to another service.
This way both activities are independently executed each with its own retry configuration and task queue.
Here is the problem. If the microservice is down, and Activity 1’s retry mechanism kicks in, then Activity 1 yields back control only after all retries have been exhausted OR when microservice is up again. This means we can post data on webhook only ONCE.
We have a usecase where we want to post the microservice response on a webhook irrespective of whether its up or down. How do we achieve this?
If i have a single activity that does the microservice call and webhook call, I cannot independently retry these steps unless I write a custom retry logic within the activity.
Can you please suggest what the best approach would be?
Could you describe what you exactly want? Do you want to run these activities in parallel? When do you want to execute the second activity after the first one starts failing?
Every time we make the microservice call, we want to post the response fetched onto a webhook. This is the prime motive.
We wanted to know the best way to express the above in the form of activities.
Case 1
Just 1 activity that does both the steps. In this case, how to ensure retries for the microservice call and webhook sending separately.
Case 2
2 activities, 1 for microservice call, 1 for webhook.
I see. I will then retry the sequence of activities from the workflow code. The second activity can be invoked asynchronously to allow retrying the first one independently.
In Java SDK, you can use the Workflow.retry method for this. If you expect many retries, the workflow must call continue-as-new periodically to limit history size.