About the UiPath Integration Services: Troubleshooting training

This training provides a deep, hands-on walkthrough of how to investigate, diagnose, and resolve issues across UiPath Integration Services. Throughout the lessons, you’ll learn how triggers work, how to debug using Application Insights, how connections are created and updated, and how to troubleshoot connector-level and activity-level problems.

Product alignment

This training was built using UiPath Integration Service, Application Insights, Connector Builder, and Microsoft/Google connector ecosystems, with examples mapped directly from UiPath’s production runtime services and backend diagnostic tools.

Learning prerequisites

To make the most of this training, you should have basic knowledge of UiPath Integration Service, APIs, OAuth 2.0 authentication, and familiarity with Application Insights, Postman, and UiPath Studio.

Audience

This training is designed for Product Support Engineers to troubleshoot customer scenarios.

Agenda

This training covers key areas around:

• Triggers, duplicate events, and debugging workflow design

• Application Insights usage and KQL log queries

• Connection creation, update failures, OAuth flows, and token refresh

• Connector Builder fundamentals and connector troubleshooting

• Microsoft Graph API, polling strategies, and trigger mechanics

• IS Activities, DAP activities, and root-cause analysis

Learning objectives

At the end of this training, you should be able to:

• Diagnose trigger issues, debug missing and duplicate events, and trace poller behavior

• Use Application Insights and KQL to identify root causes and analyze end-to-end transactions

• Troubleshoot connection creation/update failures, including OAuth, token refresh, Ezra configuration, network issues, and vendor errors

• Build and debug custom connectors using Connector Builder

• Understand Microsoft connector auth types, polling mechanisms, and Graph API behaviors

• Identify IS Activity types, limitations, and how to troubleshoot activity-level failures