Process Mining fails to load after disabling and re-enabling it

Solutions for Process Mining failing to load after you disable and enable it again, caused by stale signing key secrets that break authentication between Airflow and DataPipeline.

After you disable Process Mining and then enable it again, Process Mining fails to load and returns the following error:

Cannot read properties of undefined (reading 'toString')

The processmining, airflow, and datapipeline-api applications report a healthy state in ArgoCD, and their pods run without restarts. The datapipeline-api pod returns HTTP 401 for every request to /api/v1/pipelines/configs.

Possible cause

Disabling Process Mining removes the Airflow secrets, but leaves the DataPipeline signing key secrets in the uipath namespace in place. When you enable Process Mining again, Automation Suite generates new signing keys for Airflow and does not overwrite the DataPipeline secrets that remain. Airflow and DataPipeline then hold different keys, so authentication between the two services fails.

The affected services continue to pass their liveness probes, which is why the cluster still reports a healthy state.

Solution

Warning:

Delete only the two secrets in step 1. Do not delete datapipeline-settings-secret-encryption-key. That secret holds the data protection encryption key, and deleting it makes existing encrypted data unreadable.

1. Delete the stale signing key secrets:

   kubectl delete secret datapipeline-settings-signing-keys-secret \
                         datapipeline-settings-signing-keys-secret-23-10 -n uipath
   

2. Apply your cluster configuration to recreate the secrets from the current Airflow keys:

   uipathctl manifest apply cluster_config.json --versions versions.json
   

3. Restart datapipeline-api to load the recreated secrets:

   kubectl rollout restart deployment/datapipeline-api -n uipath
   

Verification

Check the datapipeline-api logs for the status code returned to Airflow:

kubectl logs -n uipath deployment/datapipeline-api | grep "pipelines/configs"

Requests to /api/v1/pipelines/configs return HTTP 200, and Process Mining loads.