Hello everyone,
Hope this post doesn't seem like an attack but more like an improvement suggestion.
We have a customer's Vault with 260 WF steps including 10 which are "GOTO" steps in order to bypass the infinite loop.
(https://m-files.force.com/s/article/How-to-avoid-infinite-automatic-loop-in-workflow)
We are not alone, a few posts were already made in the past because of this :
https://community.m-files.com/forums-1552881334/f/m-files-clients/3987/unjustified-infinite-loop-error-in-workflow/9796#9796
https://community.m-files.com/forums-1552881334/f/m-files-api/2271/workflow-automatic-trigger-causing-infinite-loop---workaround/5279#5279
We are thankful that you detect the possibility of an infinite loop but this is way to restrictive and definitily not "administrator friendly".
I suppose the same way you detect the infinite loop you could detect the difference between the trigger days, if the trigger property is changed in the next step, ...
In the article "How to avoid infinite loop", it is said : "Please notice that scripting is not part of standard support and this is just an example script to show how to use API. Be aware that all scripts are run at your own risk."
Well... "The pot calling the kettle black" because we could take the risks to create an infinite loop as an admin
Thank you very much to read me out, one more time hope this doesn't look like a bad review but more like constructive criticism.
P.S. I just want to change a property value after 2 days in a WF and put it in the same step. (If you do have any better idea)
Regards,
Claudio