Changing the number of retries for SAVE operations in batch and real-time data flow runs
Control how many times batch and real-time data flow runs retry SAVE operations on records. With automatic retries, when a SAVE operation fails, the run can still successfully complete if the resources that were initially unavailable become operational. The run fails only when all the retries are unsuccessful.You can control the global number of retries for SAVE operations through a dedicated dynamic system setting. If you want to change that setting for an individual batch or real-time data flow run, update a property in the integrated API.
In the navigation pane of Dev Studio, click.
In the list of instances, search for and open the dataflow/shape/maxRetries dynamic system setting.
In the dynamic system setting editing tab, in the Value field, enter the number of retries that you want to run when a SAVE operation on a record fails during a data flow run.The default value is 5.
- Creating a batch run for data flows
Create batch runs for your data flows to make simultaneous decisions for large groups of customers. You can also create a batch run for data flows with a non-streamable primary input, for example, a Facebook data set.
- Creating a real-time run for data flows
Provide your decision strategies with the latest data by creating real-time runs for data flows with a streamable data set source, for example, a Kafka data set.