OnFailure and Retry settings

An OnFailure setting can be specified for a file that a map writes to in case the map does not run successfully. If an OnFailure setting of Commit is specified, the changes to the file remain intact, even if the map does not complete successfully. If an OnFailure setting of Rollback is specified and a map does not complete successfully, the file remains in its original state. That is, if a file originally exists, it is not updated. If a file does not originally exist, it is not created.

When the Launcher settings specify OnFailure=Rollback, the File adapter can move the source-event file to an error directory when a map fails. A default error directory is always available when cooperative file listening is enabled in the config.yaml file. When cooperative file listening is disabled, an error directory is available only if you configure it in the Launcher settings.

The Retry option applies to files that exist. Retry is used for files that exist, but might be in use by applications unknown to the Launcher and cause a resource conflict. For example, a file to be opened is already open for write or a file to be opened for write is already opened for read or write.