In our current environment, retry is handled at trigger properties instead at flow service level using throwExceptionForRetry service.
As per my understanding, trigger retry happens even when the transaction failed due to non-transient error and throw exception upon retry completion.
Later we can resubmit the failed transactions from MWS.
Due to lack of support team, now we got the requirement to provide a solution which removes the dependency of support team.
In other words, resubmit the request automatically when end system is up and running again.
Initially I thought of ‘suspend and retry later’ approach at trigger level, but in case the trigger will stuck in a loop if it is a non-transient error.
Other solution, I was thinking of writing a schedule service but did not find any build-in service which can be helpful in pick and push transactions.
Please advice another approach or pointer to implement the scheduled service approach.
Please note, we are using IS – 7.1.2 and Broker – 8
Thanks in advance.