Runtime troubleshooting

Symptom

To identify a chunk of interest in the list, use the information in the following columns:

Capture ID
The registration identification number.

Upload time
Time taken for the Task Mining Agent to send chunks to the server.

Host ID
Identification string of the sender.

To retrieve the Host ID on the client side, do the following steps:

1. Right-click the Task Mining Agent tray icon on the taskbar and click About.
2. Click the Copy icon next to Host ID to copy the Host ID to the clipboard.
   

Workaround

The processing pipeline of chunks has the following phases:

Processor
The system applies the project configuration that is defined in the IBM Task Mining application. It extracts the relevant data and task events to the recorded data.

Miner
The system correlates the data that is extracted during the Processor step to generate the event log that is sent for process mining.

Process Mining Upload
The system calls the IBM Process Mining API to upload the generated event logs.

To run depend on the type of the chunk, do one of the following steps:

• For the partial chunks, run the Processor phase.
• For the end and full chunks, run all three steps.
  For the end type chunks, Miner and Process Mining Upload steps involve all the chunks in the same session. In other words, the last two steps do not start until you complete the Processor step for all the chunks of the session.

The upload of the Processor, Miner, and Process Mining Upload data assumes different states when you collect a chunk. The following image shows all the possible states:

If you see a warning status during the Miner step, expand the corresponding Capture ID to verify the error messages and other related information of a chunk.

When you do the steps, ensure that:

• Processor is always required for every type of chunk.
• Miner is required for the full and end types of chunk.
• Process Mining Upload is performed only if the Miner completes the elaboration accurately or with a warning. If an error occurs or nothing found message shows in the previous step, the system does not run the Process Mining Upload step.
  

If the Processor step for a partial chunk displays an error, the system runs the Miner and Process Mining Upload steps. The system ignores the chunks in error during these steps and includes only the chunks that were processed without errors.

Symptom

The cause of the problem might be a missing match inside the pipeline steps.

Workaround

Every data that is collected in a chunk can be downloaded from the Audit page through an encrypted compressed file. You can use this file to verify the output of each step of the Task Miner.

To download the file, do the following steps:

1. Go to the Audit page in your Task Mining project.

2. Select the chunk record.

3. Click three dots menu and download the file.

To use this troubleshooting method, you must first contact IBM Support. The downloaded file is encrypted for security. You need to use the decryption key that the IBM Support provides you to download and decrypt the file. For more information, see Downloading a capture.

Symptom

You might notice Task Mining Agent connection failures if the endpoint URL is incorrect, the endpoint is inaccessible, or the internet is down.

Workaround

Check the latest Task Mining Agent logs for more details. You can find the log file in the following directory: C:\Users\<user_name>\AppData\Roaming\IBM Task Mining Agent\logs.

To check the endpoint status, do the following steps:

1. Check whether your endpoint is correct.

   • When a connection fails, you might see the following information in the logs:

   2023-03-14 02:19:11,975 INFO  AppWindow - '': Initializing WebView
   2023-03-14 02:19:14,530 INFO  AppWindow - '': WebView initialized successfully
   2023-03-14 02:19:15,651 INFO  AppWindow - 'https://example_endpoint.com': Initializing WebView
   2023-03-14 02:19:16,369 INFO  AppWindow - 'https://example_endpoint.com': WebView initialized successfully
   2023-03-14 02:19:17,195 WARN  AppWindow - Error on navigating to 'https://example_endpoint.com/'. Status: 'HostNameNotResolved'
   2023-03-14 02:19:17,872 WARN  AppWindow - Error on navigating to 'https://example_endpoint.com/'. Status: 'ConnectionAborted'
   2023-03-14 02:19:22,927 WARN  AppWindow - Error on navigating to 'https://example_endpoint.com/'. Status: 'ConnectionAborted'
   2023-03-14 02:19:53,026 WARN  AppWindow - Error on navigating to 'https://example_endpoint.com/'. Status: 'ConnectionAborted'
   2023-03-14 02:20:53,076 WARN  AppWindow - Error on navigating to 'https://example_endpoint.com/'. Status: 'ConnectionAborted'
   

   Check whether the endpoint in the appsettings.json file is correct and try connecting to it by using a browser.
   appsettings.json file is in the folder where the Task Mining Agent is installed. You can manually correct the endpoint details and save the changes.

2. Check whether your endpoint is reachable.

If the endpoint access URL is unable to resolve or if you have internet issues, try connecting again after some time.

Symptom

The error indicates that you do not have the necessary authorization to access Task Mining Agent.

Workaround

Contact the system administrator who can provide you with the authorization to use the Task Mining Agent from the User Management form in IBM Process Mining.