How to Customize the Failure Occurrence Count to Control Data Refresh Disabling

Published:

By default, data refresh will be disabled after five consecutive failures in Bold BI. Users can customize this value to their desired count by following the steps outlined in this article.

Advantages of Customizing Failure Occurrence

Customizing the failure occurrence count allows you to better manage and control your data refresh processes. You can set thresholds that align with your organization’s tolerance for errors, ensuring that temporary issues do not immediately halt data refresh operations while still protecting against prolonged failures.

Steps to Update the Failure Occurrence Count from UI

Step 1: Go to Settings page by using the URL mentioned below.

{yourdomain}/ums/administration

Step 2: In the Settings page, click the Configuration tab.

Step 3: In the configuration dropdown menu select the bi/config.xml file.

Step 4: Select the node FailureOccurrence, set your desired value, and save the settings.

Please add the node to set the value if the FailureOccurrence node is unavailable in the configuration file.

Steps to Manually Update the Failure Occurrence Count for Different Environments

Windows

Open the config.xml file located at:

{deployment_location}\app_data\bi\configuration\config.xml

Set the FailureOccurrence node to true. If the node is not present, add the following line:
```
<FailureOccurrence>{desired_count}</FailureOccurrence>
```
Save the file.

Linux

Open the terminal and navigate to the deployment location:

cd /var/www/bold-services/application/app-data/bi/configuration/

Open the config.xml file using nano:
```
sudo nano config.xml
```
Set the FailureOccurrence node to true. If the node is not present, add the following line:
```
<FailureOccurrence>{desired_count}</FailureOccurrence>
```
To save the changes, press Ctrl + X, then Y, and hit Enter.

Docker

Access the Docker container using the following command:

sudo docker exec -it <container id or container name> bash

Navigate to the configuration directory:

cd /application/app-data/bi/configuration/

Open the config.xml file using nano:
```
sudo nano config.xml
```
Set the FailureOccurrence node to true. If the node is not present, add the following line:
```
<FailureOccurrence>{desired_count}</FailureOccurrence>
```
To save the changes, press Ctrl + X, then Y, and hit Enter.

Kubernetes

List the pods and exec into one of the pods:

kubectl get pods
kubectl exec -it {Podname} -n {namespace} -- bash

Install nano if it is not already installed:
```
apt-get update
apt-get install nano
```

Navigate to the configuration directory:

cd /application/app_data/bi/configuration/

Open the config.xml file using nano:
```
sudo nano config.xml
```
Set the FailureOccurrence node to true. If the node is not present, add the following line:
```
<FailureOccurrence>{desired_count}</FailureOccurrence>
```
To save the changes, press Ctrl + X, then Y, and hit Enter.

After completing the above steps in the respective environment, restart the Bold BI application to apply the changes.

Example Results:

By configuring the failure occurrence count to three, the data source refresh will be disabled after three consecutive failures instead of the default five. You can view the details in the refresh history dialog.