Sometimes the user expects errors for a part of records in a process and they are inevitable, yet this problem is known and it is preferable to ignore these failed messages and get final status of the process as SUCCESS. And in this situation failure tolerance parameter comes to aid. It determines how many failed records within a process cause the whole process FAILED.
...
| Code Block | ||
|---|---|---|
| ||
<COL TAG="W_USE_STREAM_FAILURE_TOLERANCE" EXPRESSION="'1'" USERDESCRIPTION="Use the preset stream Failure Tolerance value for TSR status. yes(1) or no(0)"/> |
For Warehouse Preproc stream you can switch Failure Tolerance type between batches and separate records by setting W_FAILURE_TOLERANCE_TYPE config parameter to either BATCH or RECORD:
| Code Block | ||
|---|---|---|
| ||
<COL TAG="W_FAILURE_TOLERANCE_TYPE" EXPRESSION="'BATCH'"/> |
| Info |
|---|
Please note, that W_FAILURE_TOLERANCE_TYPE has sense only for Warehouse Preproc, as other streams do not handle batches of multiple records |
Forcing Custom Failure Tolerance in the Control Message
...
In this case, if actual percentage of failed records is less than 20%, the step will be shown as SUCCESS, yet the final status of the whole workflow may be displayed as FAILED. In this case thorough investigation of message details for each step should be performed to locate the issue.
| Info | ||
|---|---|---|
| ||
| If neither W_USE_STREAM_FAILURE_TOLERANCE parameter is specified, nor FailureTolerance in the CM, the final TSR status will be FAILED in case any record fails (failure tolerance = 0%) |
...