Platform Deployment Guide › Content Services › Retrying Failed Indexing Jobs › How Retries Are Tracked

How Retries Are Tracked

Due to unforeseen circumstances, the content indexer may not process some events. The EVLs of these failed events are not placed in the ‘no retry’ folder because they are scheduled to be retried. If the event fails permanently, you want to prevent retry jobs from processing the same failed event repeatedly.

The content indexer prevents this endless loop by keeping a record of how often it retried to process an EVL. Set the OPT parameter EVLRETRIES to control how often jobs are reprocessed.

1. Each time a retry job reprocesses an EVL, it increments a counter (‘Retries=’) which is stored in the EVL.
2. If the job retries an EVL, and it fails, and the retry counter exceeds the EVLRETRIES value, then the EVL is written to the ‘No retry’ folder under the subfolder ‘Struck out’. When the EVL is written to the ‘struck out’ folder, the failure folder structure persists.
3. Retry jobs do not target the ‘No retry’ folder and the failing job is not reprocessed.