Hey @BlueFlamingo , great question!
The how to handle this really depends on what you want to happen. It sounds like if there is no file (job failing) you want the entire sequence to stop?
If so, you could create some logic in Mitto that could help accomplish this. I don’t know the full details of how you have your jobs and sequences nested but here is a simple and an advanced version of a potential solution:
Simple
The simplest approach but maybe not feasible depending on your setup would be to put the SFTP job into a Master Sequence, separate from all the other jobs within the sequence and set the Master Sequence “Continue on Error” to “False”. If that SFTP job positioned before the child sequence fails, everything will stop and the child sequence or series of ETL jobs will not run.
Advanced - Uses Webhooks so positioning or locations within a sequence don’t necessarily matter as much.
- Create a master sequence that contains the child sequence of jobs that should or shouldn’t run depending on the result of the SFTP job and set the Master Sequence “Continue on Error” to “False”.
- In the Master Sequence, before the child sequence, add your SFTP job.
- Within your SFTP job, add a webhook that is set to trigger on JOB_SUCCESS. For the url, have it target the child sequence inside of the Master Sequence (or wherever you want it to live) and send the start action to that sequence. Here is an exact example of what I’m referring to: Add Webhooks to Any Individual Job or Sequence in Mitto | Zuar
If the above is built correctly, you’ve essentially implement logic between the SFTP job and the dependent sequence, which is all organized within the Master Sequence. When the SFTP job succeeds, it will fire off the webhook to kick off the child sequence. When it fails, nothing will happen since you have the Master Sequence set to FALSE for continue on error!