- Primeros pasos
- Tutoriales
- Proyectos de automatización
- Crear automatizaciones
- Fundamentos de la automatización
- Repo. de objetos
- Mejores prácticas de automatización
- Tutorial: Crear una tabla dinámica
- Tutorial: Iterar a través de las filas de una tabla
- Tutorial: Comparar archivos de Excel y envío de errores de conciliación por correo electrónico
- Tutorial: Extraer datos de correos electrónicos automatizados y trasladarlos a una aplicación de escritorio
- Tutorial: Filtrar datos en Excel
- Tutorial: Formatear celdas
- Tutorial: Añadir información en los archivos de una carpeta a un archivo de Excel
- Tutorial: Añadir sus propias fórmulas al cuaderno del proyecto
- Automatización de PowerPoint
- Automatización de datos
- Actividades comunes
- Automatización de Google Workspace
- Automatización de OneDrive y SharePoint
- Solución de problemas
Guía del usuario de StudioX
Debugging Your Automation Project
La depuración es el proceso de identificar y eliminar los errores que impiden que el proyecto funcione de forma correcta. Se recomienda realizar la depuración durante la fase de diseño del proyecto de automatización, a nivel de actividad, archivo y proyecto.
Debugging can be performed using several options, defined in the ribbon and explained below.
To start debugging your project, click the Debug tab to access the debugging options available in StudioX. You can start the debug process by clicking Debug ribbon button or using F5.
The default action under the Run/Debug ribbon button can be configured from Backstage View > Settings > Design > Run/Debug Default Behavior option. Pick from Debug File, Run File, Debug Project, or Run Project, as the default action when clicking the button.
StudioX provides several different actions to help with the debugging process, located in the Debug ribbon tab.
Use Next Step to debug activities one at a time. When this action is triggered, the debugger opens and highlights the activity before it is executed. The keyboard shortcut for Next Step is F11.
Retry re-executes the previous activity, and throws the exception if it's encountered again. The activity which threw the exception is highlighted and details about the error are shown in the Debugging panel.
The Ignore action can be used to ignore an encountered exception and continue the execution from the next activity so that the rest of the project can be debugged.
Esta acción es útil al omitir la actividad que lanzó la excepción y continúa depurando la parte restante del proyecto.
Restart is available after an exception was thrown and the debug process is paused. The action is used for restarting the debugging process from the first activity of the project.
Ten en cuenta que al utilizar esta opción después de usar la acción Ejecutar desde esta acción de actividad la depuración se reinicia desde la actividad indicada anteriormente.
Breakpoints are used to purposely pause the debugging process on an activity which may trigger execution issues. You can set a condition and/or hit count to a simple breakpoint and turn it into a conditional one. Adding logging results turns the conditional breakpoint in a conditional tracepoint. Adding only a logging message transforms the breakpoint to a simple tracepoint.
Read more about Breakpoints and how to use them in our in the StudioX guide.
Break allows you to pause the debugging process at any given moment. The activity which is being debugged remains highlighted when paused. Once this happens, you can choose to Continue, Next Step, or Stop the debugging process.
The Execution Trail ribbon button is disabled by default. When enabled, it shows the exact execution path at debugging. As the process is executed, each activity is marked in the Designer panel, showing you the execution as it happens:
- executed activities are marked in green;
- partially executed activities are marked in orange;
- activities that threw an exception are marked in red.
-
Las actividades no ejecutadas no se marcan de ninguna manera;
Si se habilita, los elementos de la IU se resaltan durante la depuración. La opción puede usarse tanto con la depuración regular como con la de paso a paso.
If enabled, debugged activities are displayed as Trace logs in the Output panel. Note that the Highlight Elements and Log Activities options can only be toggled before debugging, and persist when reopening the automation project.
Logs are automatically sent to Orchestrator if connected, but you can have them stored locally by disabling the Allow Development Logging option from the Robot Settings tab in the Add or Edit user window.
Desactivar las Actividades de registro podría ser una forma de enviar archivos de registro más pequeños a Orchestrator.
De forma predeterminada, el depurador registra las actividades para que cada paso aparezca en el panel de Salida. Se recomienda dejarla activada para facilitar el rastreo, como se puede ver en la siguiente imagen:
This debugging feature is disabled by default. When disabled in the ribbon, it throws the execution error and stops the debugging, highlights the activity which threw the exception, and logs the exception in the Output panel.
When enabled, the exception is logged in the Output panel and the execution continues.
%localappdata%\UiPath\Logs folder where logs are locally stored. The naming format of log files is YYYY-DD-MM_Component.log (such as 2018-09-12_Execution.log, or 2018-09-12_Studio.log). Read more about logging in the Studio guide.
