process-mining
2023.10
false
- Release notes
- Before you begin
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- App templates
- Additional resources
- Out-of-the-box Tags and Due dates
- Editing data transformations in a local environment
- Setting up a local test environment
- Designing an event log
- Extending the SAP Ariba extraction tool
- Performance characteristics
Process Mining
Last updated Jun 11, 2025
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.
The Process Mining cluster uses Dapr in default mode, which is incompatible with Redis cluster mode.
Re-configure Dapr with cluster mode.
Attention: 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
kubectlin 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-broadcastkubectl edit Component -n uipath dbt-execution-broadcast - Add the following configuration inside
spec: metadata:- name: redisType value: clusterImportant: Ensure that the above configuration is at the same indentation asThe following illustration shows an example.redisHost. - 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-cooperativekubectl 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-eventskubectl edit Component -n uipath process-mining-events - Restart the deployments for
process-miningandprocess-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-miningkubectl 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
