- Release notes
- Task Mining overview
- Setup and configuration
- Notifications
- Task Mining
- Additional resources
DEPRECATEDRunning analysis
For a Data Analysis, we recommend 50K actions as a good baseline. The model can support up to 200K actions collected in a project. As a quick way of estimating, an active user typically provides 200-1K actions per hour, depending on the scenario they are recording.
To run the analysis, follow the steps below:
- On the Projects page, select the project for which you want to run analysis.
On the Projects insights tab you can check out the percentage and number of actions captured.
-
Select Run analysis to start the process.
-
A pop-up window recommends having at least 50,000 actions captured for optimal results. If you don't reach the optimal number, you can select Run anyway.
Important: Running an analysis consumes 5,000 AI Units per analysis, regardless of the number of actions. Make sure you allocate AI units to your tenant before running the analysis. See Prerequisites for enabling the service.For more information about AI Units, refer to the Service licensing page in the Overview guide.™You can allocate AI Units to a tenant from the license allocation window corresponding to the desired tenant in the Automation CloudTMAdmin section. Refer to the Allocating licenses to tenants page in theAutomation CloudTM guide.
-
An informational message is displayed saying that the process has been started and an email is sent when the analysis is ready.
-
When the results of the analysis are ready, you'll receive an email. Inside the email, you can select See Discovered Tasks now to see the discovered tasks. The analysis results are uploaded automatically to the Task Mining project.
If the amount of captured actions is insufficient for a good result, the analysis can be completed without significant results. You are informed about the results via email, and a banner is displayed on the Projects Insights page. In this case, it's recommended to capture more actions.
Generating an analysis result might cause errors. If this scenario happens, a banner appears on the Project Insights page, with a clickable link to contact support to resolve the issue promptly.