Hello Temporal team,
Here is the scenario:
Say we have 10 API requests resulting in 10 workflows calling downstream service A. Service A might become overloaded or experience an outage, causing Temporal activity retries to occur. Is there a way in Temporal to ensure that the first request’s activity retry gets serviced before the 2nd, 3rd, etc…?
I’'m trying to avoid a race condition where 2nd, 3rd, etc… gets priority and the first request continues to retry, which would lead to long processing time for the user.
I was thinking of using a Kafka queue between Temporal activity and the downstream service, but this may be redundant.