UiPath Task Capture

The Task Capture Guide

Troubleshooting Guide

On this page, you can find basic troubleshooting steps for some of the most common issues that can occur while working with Task Capture.

Troubleshooting a Broken Template

If a broken template error message is displayed while trying to import a customized template to Task Capture please follow the below steps in order to try and resolve the issue:

🚧

Important:

Task Capture only accepts .ssword files (default file type created from Task Capture). If it's different than .ssword or you created it either manually or using other tools, it's not accepted by the application. Please follow the steps from the Creating your own Word Template page to find out how to create a custom template and Exporting a Template to export it as the .ssword file.

In case the invalid .ssword file was created using Task Capture let's dive deeper and discover what might go wrong with it.

  1. Access the folder from your PC where you store the template and make a copy of the file.
  2. Change the format of the file copy to .zip.
  3. Check the files and folders in the created .zip archive. It should contain template folder and config.xml file.
  4. In case the structure of the folders is different or any file is missed but you can access the .docx file of your template, please extract it from the .zip archive and follow the steps from the Creating your own Word Template page to create a new template from it.
  5. Otherwise please proceed to open the log file from Task Capture.
    The log file is frequently requested during the troubleshooting process. To retrieve it simply access Task Capture top-panel menu > Help > Open Logs Folder.
  6. Open a Support request by completing this form. Add the Logs File to the ticket created for the issue and the .ssword file that can not be imported.

UiPath Studio Export Error

If an error is displayed wile trying to expert your process as XAML file to Studio apply te following troubleshooting steps:

  • Check if the problem is caused by the .ssp file by following the below steps:
    1. Access the process in Task Capture.
    2. Export the workflow as Word Document.
    3. If this works, open a different .ssp file in Task Capture.
    4. Export it in Studio as XAML file.
  • Chech if your file contains broken steps by following the below steps:
    1. Access the process in Task Capture.
    2. Delete the first half of the available steps.
    3. Export the remaining process it in Studio as XAML file.
    4. If this works access again the process in Task Capture.
    5. Delete the other half of the available steps.
    6. Export the remaining process in Studio as XAML file.
    7. Access again the process in Task Capture.
    8. When the broken step is found Delete its title and description. The issue is usually caused by some characters.

Actions not Recorded After Starting the Capture Process

Check the below causes:

  • Check the writing permissions for user data folders.
    Task Capture uses %localappdata% as the installation folder and %appdata% and %temp% folder as temporary storage. If you have read-only access to user data folders, this can prevent Task Capture to write particular data.
  • Check the Anti-Viruses logs.
    Task Capture uses low-level hooks via the SetWindowsHookEx WinAPI method this is why some Anti-Viruses detect Task Capture as a spying software.

If the issue is not caused by one of the above points please proceed to open the log file from Task Capture. The log file is frequently requested during the troubleshooting process. To retrieve it simply access Task Capture top-panel menu > Help > Open Logs Folder.
Open a Support request by completing this form. Add the Logs File to the ticket created for the issue and the .ssword file that can not be imported.

Updated 25 days ago


See Also

FAQs

Troubleshooting Guide


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.