Is there any way to reset the retry counter = 0 after a failed activity recovers and start heartbeating.
I have a long running Activity (think weeks+) that maintains its liveliness via heartbeat. Obviously the activity gets killed and respawned multiple time due to ec2/pod rebalancing.
Ideally I’d expect the retry counter / max attempts to reset once the activity starts heart beating again but it does not. I am currently doing workaround by setting a very high retry count like 30+ to account for infra failures. But ideally I’d want the activity to fail if more than 5 consecutive failures.
Is there any way I can reset the counter once the activity start heartbeating again ? (that should be the default behaviour IMO.