This tutorial shows how to continue a loop after an error in Advanced ETL Processor. Use it when one bad file, record, email, or JSON item should be logged and skipped instead of stopping the whole package. One awkward row should not get to hold the entire workflow hostage.
What You Will Learn
- Route loop errors to a handling action instead of stopping the package.
- Return from the error path to the next loop iteration.
- Choose the right loop action for files, records, emails, or JSON data.
- Use debugging and variables to see which item failed.
Before You Start
Use a test repository or safe sample data while following the tutorial. Production jobs are a poor place to experiment.
Loop Examples And Related Actions
This tutorial uses the package error path to keep a loop moving after one item fails. In practice, the error branch should record the problem, clean up if needed, and send execution back to the loop. That way the package handles bad input like an adult, not like a printer asked to work on Monday morning.
The loop examples documentation covers Up Loop, Down Loop, File Loop, Files Loop, Database Loop, Office 365 Email Loop, IMAP4 Email Loop, JSON Array Loop, and JSON Object Loop.
Related action docs include IMAP4 Email Loop Action, Office 365 Email Loop Action, File Loop Action, Files Loop Action, Database Loop Action, Down Loop Action, Up Loop Action, JSON Object Loop Action, and JSON Array Loop Action.
For troubleshooting, use package debugging and working with variables to log the current loop item before moving on to the next one.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.