Automation Suite on Linux installation guide

Last updated Mar 9, 2026

Configuring Dapr with Redis in cluster mode

If you are using Redis in cluster mode, you may encouter issues when working with the Process Mining Data transformations editor.

Possible cause

The Process Mining cluster uses Dapr in default mode, which is incompatible with Redis cluster mode.

Solution

Re-configure Dapr with cluster mode.

Note:

It is assumed that you have knowledge of kubectl.

Take the following steps to manually re-configure Dapr with cluster mode.

Go to Applications in ArgoCD, and select processmining. The following illustration shows an example.
Select the Details tab. The following illustration shows an example.
Locate the SYNC POLICY section, and select DISABLE AUTO-SYNC. The following illustration shows an example.
Select OK to confirm auto-sync. The following illustration shows an example.
Go to the terminal and ensure that you are running kubectl in the Service Fabric cluster context.
Run the following command to edit the Component called dbt-execution-broadcast. This opens the Component configuration in the default text editor.
```
kubectl edit Component -n uipath dbt-execution-broadcast
kubectl edit Component -n uipath dbt-execution-broadcast
```
Add the following configuration inside spec: metadata:
```
  - name: redisType 
    value: cluster
  - name: redisType 
    value: cluster
```
Important:
Ensure that the above configuration is at the same indentation as redisHost.

The following illustration shows an example.
Save the configuration and exit. This ensures that the Component is updated.

Repeat steps 6 to 8 for the Component dbt-execution-cooperative .

kubectl edit Component -n uipath dbt-execution-cooperative
kubectl edit Component -n uipath dbt-execution-cooperative

Repeat steps 6 to 8 for the Component process-mining-events.

kubectl edit Component -n uipath process-mining-events
kubectl edit Component -n uipath process-mining-events

Restart the deployments for process-mining and process-mining-dbt-exec.

kubectl rollout restart  -n uipath deploy/process-mining-dbt-exec deploy/process-mining
kubectl rollout status  -n uipath deploy/process-mining-dbt-exec deploy/process-mining
kubectl rollout restart  -n uipath deploy/process-mining-dbt-exec deploy/process-mining
kubectl rollout status  -n uipath deploy/process-mining-dbt-exec deploy/process-mining

Dapr is now configured with cluster mode and the Process Mining Data transformations editor should work as expected.

On this page

Possible cause
Solution

Was this page helpful?

PREVIOUSAfter Disaster Recovery Dapr is not working properly for Process Mining

NEXTUnable to connect to AutomationSuite_ProcessMining_Warehouse database using a pyodbc format connection string

Automation Suite on Linux installation guide

Possible cause​

Solution​

Was this page helpful?

Possible cause

Solution