A Loop in the new automations would be great. Like in the Custom Transformers.
Automations with a loop
FME Form
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Agree. Some kind of workspace could fail the translation with an external temporary cause (e.g. network traffic issue). Loop could be used to recover such a failure.
For example, it would be realized if an Action component could determine the next action (succeeded or failed) according to a condition (e.g. whether the number of performing the action is less than a specified number).
In addition, "Wait" action which works like the Decelerator might also be useful in some cases.
Example: It would be nice if the "Action" could determine the next action according to whether a condition is satisfied.
@takashi's reason explained below is the exact reason I was looking for this as an option. My Workspace, scheduled to execute every hour, occasionally fails because an external resource being queried sometimes gets bogged with traffic and the query timesout. I have the automation then set, when this Workspace fails, to execute another Workspace that simply delays 5min and upon successful completion of the delay executes the original Workspace again. However, this attempt could fail as well, and because there is no LOOP, it will remain undone until the next scheduled event.
I can third this request. Right now we have to use PRIORITY and a submission bench (priority 50) and a job checker bench, (priority 200). Right now, the job checker bench will always be the last bench in que to run (that is until priority is completely removed from server [not sure if that is still in FME's roadmap, priority does have uses!!!]), which allows us to submit all jobs with out having our submitter to wait. We then check our submitted jobs for the night, to see what failed (usually HTTP issues with AGOL). If any failures have occured, we want them run again, which re-runs our submitter with the failed jobs only. If they fail a second time, it likely is not a traffic issue or is something else that needs our attention.
Looping automations would take care of that if the standard looping parameters are included (how many times before escape, conditions for escape, etc.)
We are pleased to announce that in FME Server 2020.0 there is an option for users to enable Looping in Automations!
Try it out today with the latest FME Server 2020.0 beta and let us know what you think! (Note: Requires Build 20162 or newer.)