Hi, all:
Currently, service comb saga would keep trying transaction part when using forwardPolicy. The policy is sufficient for some situations, such as network fluctuations or service unavailability temporarily. But for other situations like wrong address, wrong params or wrong SQL, it is possible to cause saga retry infinitely. So, I recommend that Saga should be able to configure the maximum of retries for forwardPolicy. When users configure the maximum of retries and transaction failed repeatedly, Saga should throw exception or do backward. Best Wishes & Regards
