> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fynapse.app/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fynapse.app/_mcp/server.

# Reprocessing Configuration

> Learn about reprocessing configuration in Fynapse.

## Overview

The **Reprocessing** screen allows users with the Fynapse System Administrator role to define when and how often automatic reprocessing of failed events should be triggered. Additionally, the screen allows setting a maximum number of reprocessing retries that takes into account both automatic and manual reprocessing runs.

> **Info**
>
> Please note that reprocessing does not include errored Journals ingested via the Adjustment Portal
> or via Journal Import step in Flows.

## Reprocessing Screen

The **Reprocessing** screen comprises the following elements:

* The **Edit** button - click it to configure settings for automatic reprocessing
* The **Scheduler type** panel - use this panel to decide if automatic reprocessing will be run on specific dates, on a basis of a defined frequency, or it should be disabled.
  > **Info**
  >
  > If you choose **Disabled**, then the automatic reprocessing will be disabled. To reprocess failed data, users will have to do it manually using the **Download Errors** screen.
* The time settings panel - use it to define frequency details. While configuring the schedule, you need to remember that time interval between following reprocessing repetitions must be at least 180 minutes. If you configure shorter time interval, then you will not be able to save this configuration.
  * **Frequency** - if you choose this option, then you need to define at least one configuration in **Primary frequency**. This panel comprises of:
    * **Primary frequency**:
      * The **Repeat** list - use it to select how often automatic reprocessing must be triggered. You can select a particular option only once.
      * Time settings - use it to set when exactly automatic reprocessing must be triggered. The type of time setting depends on the option you select from the **Repeat** list.
      * The **Add** button - click it to add another time setting (it denotes another repetition of reprocessing within a given frequency)
      * The trash bin icon - click it to delete a particular setting row
      * The **Add additional frequency** button - use it to add another frequency setting
  * **Specific dates** - if you choose this option, then you need to define at least one date and time. To add another specific date (it denotes another repetition of reprocessing), click the **Add** button. Note that each specific date can be used only once. To delete the specific date, click the trash bin icon.
  * The **Limit** panel - use this panel to set a maximum number of reprocessing retries for failed events. The setting takes into account both automatic and manual reprocessing runs. However, if the scheduler type is set to **Disabled**, then the limit is set only for manual reprocessing. Once the limit for a failed event is reached, and the cause of its failure is not identified, it stays in the failed status permanently and is not reprocessed anymore.
    > **Tip**
    >
    > The default number of retries is set to 30. However, we recommend setting the limit to a lower one to enable system operators to remove a cause of an error.
* The action buttons:
  * The **Save** button - click it to save the settings. While configuring the schedule, you need to remember that time interval between following reprocessing repetitions must be at least 180 minutes. If you configure shorter time interval, then you will not be able to save this configuration.
  * The **Cancel** button - click it to discard your changes

> **What happens when I change the number of reprocessing retries?**
>
> The retry count is stored with the record and is evaluated against the current retry limit during each reprocessing run.
> If you decide to change the number of retries attempted for failed records you need to consider the following:
>
> * If the limit is increased before the next run, a record that previously exhausted its retries may become eligible for another attempt and will be resubmitted, under the condition the limit is increased before the next eavaluation of the retry limit.
> * If the limit is increaed after a record has exhausted its retries and the evaluation of the limit for the next run has already happened, the record will not be reprocessed.

> **Warning**
>
> Please note that the minimum number of reprocessing retries is 1, i.e. it is impossible to set the number of retries to zero.
> Moreover, the number of processing retries cannot be applied selectively on Entities or error types, as it is a global paramerer.

## Tutorials

#### How to Configure the Reprocessing Schedule?

> **Info**
>
> While configuring the schedule, you need to remember that the time interval between the following reprocessing repetitions must be at least 180 minutes. If you configure a shorter time interval, then you will not be able to save this configuration.

1. Go to **System Configurations > Reprocessing**.
2. Click the **Edit** button.
3. In the **Scheduler type** panel, select the proper checkbox.
4. In the time settings panel, configure reprocessing frequency details:
   1. If you select the **Frequency** option:
      1. You need to define at least one configuration in the **Primary frequency** panel by selecting an option from the **Repeat** list and configuring its details. Click the **Add** button to add more settings.
      2. If you need more than one frequency, click the **Add additional frequency** button and configure it in the same way as you did while defining the primary one. Note that each frequency setting must be unique within one frequency base, for example, you cannot add this setting *Wednesdays at 11:00* *AM* more than once.
   2. If you select the **Specific dates** option, then by clicking the **Add** button add as many dates as you need. The number of configured dates denotes how many times reprocessing will be triggered. Note that each specific date must be unique, for example, you cannot add this setting *25.07.2025 at 11:00* *AM* more than once.
   3. If you select the **Disabled** option, then the automatic reprocessing will be disabled. To reprocess failed data, users will have to do it manually using the [**Download Errors**](/documentation/data-management/error-management-service/overview) screen.
5. Into the **Maximum number of retries for failed event** type a number of maximum reprocessing retries.
   > **Tip**
   >
   > The setting takes into account both automatic and manual reprocessing runs. However, if the scheduler type is set to **Disabled**, then the limit is set only for manual reprocessing.
6. Click the **Save** button to save the changes or the **Cancel** button to discard them.

## Learn More

* [Errors](/documentation/data-management/error-management-service/errors)
* [Consolidated Error List](/documentation/data-management/error-management-service/consolidated-error-list)