If you add multiple execution steps to a job, FlowForce will process them sequentially, starting with the first (topmost) step down to the last step. This rule also applies to any sub-steps that a step may have. The diagram below illustrates this scenario.
By default, if FlowForce encounters an error, processing stops, and any subsequent steps are not executed. Sometimes, you might not want to break the execution of the whole job if a step fails. In this case, you can configure a function that will prevent the job execution from stopping even after an error has occurred. Note that this behavior can apply only to steps that call the following functions:
•All functions under /system/filesystem
•All functions under /system/ftp
•All functions under /system/mail
•The /system/shell/commandline function
Sequential processing is only one of the ways to process jobs and may not always suit your needs. For more advanced processing options, see the following topics: