I have been going through the temporal go developers guide.
One thing I noticed in the “Activity and Workflow Retries” section is that temporal currently supports exponential backoff retry policy.
However, for our use cases, we wanted to explore options on how to add custom retry policies that suites our business requirement.
e.g. one of the policies could be a hybrid policy where the first few attempts are at regular intervals (a little more aggressive) and switch to exponential backoff after a threshold, to avoid overwhelming the systems involved.
- I would want to understand if there is any way to enforce this in temporal workflow currently?
- Is there any plan for extending retry policies to more algorithms than what we have currently say exponential backoff with jitter, random interval, etc. ?