When one creates a state machine, the maximum number of retries for a state is set at the class level. However, a use case of state machines is to create generic state machines where the state name is 'StateX' and URI is specified only at the instance level, not the class. In this case, to stay generic, one is tempted to set the maximum number of retries to a very high number for each state, to cover whatever situation at the instance level.
Allowing to override the maximum number of retries at the instance level would help creating generic state machine classes (scaffolds) with no maximum retries set, and then let the instance specify the maximum retries based on the actual URI.
According to @mkanoor, the max_retries can already be set at the instance level in the backend code, but the UI currently doesn't support it. So I create this issue to politely ask for someone to add this in th Classic UI.
Created attachment 1474269 [details]
Fixed! I can confirm max_retries is at instance level in StateMachines UI.
Rechecked it by executing state machine via simulation.
1. Created domain and class
2. Created `meth1` method and `meth1_instance` instance in class
3. Created state machine, added instance there and pointed value to `meth1_instance`
4. Added max_retries value as 3 in instance and 2 in class
5. In simulation, used `Call_Instance` with namespace, class and instance with Attribute/Value Pairs.
After submiting request we got three retries, which was what we were expected.
Found features works very well, great work folks!
Verified on: 126.96.36.199.20180725145922_d299ff5