Study guide
18.2 Running Local Triggers & the Event Inspection Tool
UiPath Automation Developer Professional UiPath-ADPv1
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Blueprint Map
1.1 About the UiPath-ADPv1 Exam: Format, Fees & Policies 1.2 The Exam Topics Mapped to This Guide & a Study Plan
2 Chapter 2: REFramework Architecture & State Dynamics
2.1 State Machine Architecture & The Four Core States 2.2 Configuration Management: Settings, Constants, and Assets 2.3 Transaction Types & The Dispatcher vs. Performer Architecture 2.4 Adapting REFramework: Tabular Data, Collections & Linear Processes
3 Chapter 3: REFramework Exception Handling & Recovery
3.1 BusinessRuleException vs. System.Exception Handling Patterns 3.2 Retry Mechanisms: Queue Retries vs. REFramework MaxRetryNumber 3.3 Consecutive System Exceptions & Graceful Process Termination
4 Chapter 4: State Machines, Custom Log Fields & REFramework Testing
4.1 Building State Machine Projects in Studio 4.2 Logging Levels, Robot Logs & Custom Log Fields in REFramework 4.3 Testing a REFramework Project With and Without Orchestrator Queues
5 Chapter 5: LINQ Queries & DataTable Operations
5.1 LINQ Essentials for Collections & Filtering 5.2 Advanced DataTable Querying with LINQ 5.3 In-Memory DataTable Transformations & Column Operations
6 Chapter 6: Regex, DateTime, JSON & Invoke Activities
6.1 Regular Expressions & Text Parsing for Automation 6.2 DateTime Formatting, Timezone Conversions & TimeSpan Calculations 6.3 JSON Parsing, JSONPath & Serialization with Newtonsoft.Json 6.4 Invoke Method & Invoke Code Activities 6.5 Data Referencing in Invokes: DataTable, List & Dictionary Arguments
7 Chapter 7: Modern UI Automation & Unified Targeting
7.1 Modern Design Experience & The Unified Target Concept 7.2 Anchors, Relative Elements & UI Automation Activities 7.3 Dynamic Selectors, Variables & Wildcards in Selectors
8 Chapter 8: Object Repository, Computer Vision & Remote Runtime
8.1 Object Repository & UI Descriptor Libraries 8.2 AI Computer Vision for Unattended & Remote Interfaces 8.3 Automation in Virtual Environments & UiPath Remote Runtime
9 Chapter 9: Advanced UI Automation: Browser Modes, Agentic UI & macOS
9.1 Browser Automation with the WebDriver Protocol 9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent 9.3 macOS Automation: Native Apps, Office Apps & AppleScript
10 Chapter 10: Advanced Control Flow & Exception Architecture
10.1 Flowcharts, Sequences & Parallel Control Flow Patterns 10.2 Global Exception Handler Architecture & ErrorAction Directives 10.3 TryCatch, Retry Scope & Custom Exception Architectures
11 Chapter 11: Orchestrator Queues & Transaction Management
11.1 Queue Architecture, SpecificContent & Transaction Lifecycles 11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling 11.3 Bulk Operations, Transaction Status Updates & Queue Triggers
12 Chapter 12: Orchestrator Tenant & Folder Entities
12.1 Asset Types, Per-Robot Assets & External Credential Stores 12.2 Modern Folder Hierarchy, User/Robot Assignment & Permissions 12.3 Storage Buckets, Webhooks & Environment Promotion 12.4 Orchestrator Tags: Labels, Properties & Governance
13 Chapter 13: Unattended Execution, API Triggers & Cloud Robots
13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes 13.2 API Triggers: Starting Jobs from External Systems over HTTP 13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options
14 Chapter 14: Monitoring, Recording & Solutions Management
14.1 Orchestrator Monitoring, Trigger Alerts & Job Health 14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs 14.3 Solutions Management: Packaging and Deploying Automations with Their Resources
15 Chapter 15: Debugging, Remote Debugging & Profiling
15.1 Studio Debugging Tools: Breakpoints, Panels & Execution Control 15.2 Remote Debugging: Remote Machine and Unattended Robot Connections 15.3 Profile Execution: Finding Performance Bottlenecks in Studio
16 Chapter 16: RPA Testing & Test Suite
16.1 UiPath Test Suite Overview, Test Cases & Given-When-Then Structure 16.2 Data-Driven Testing, Test Verification Activities & Mock Activities 16.3 CI/CD Pipelines with uipcli & Test Manager Traceability
17 Chapter 17: Long-Running Workflows, Action Center & Apps
17.1 Long-Running Workflows: Persistence, Suspend and Resume 17.2 Action Center & Human-in-the-Loop Orchestration 17.3 UiPath Apps: Action Apps, Automations & Integration Service
18 Chapter 18: Trigger-Based Attended Automation & Callouts
18.1 Trigger-Based Attended Automation: Forms, Triggers & Global Variables 18.2 Running Local Triggers & the Event Inspection Tool 18.3 Callouts & Forms for Attended Guidance
19 Chapter 19: UiPath Assistant & Robot Sessions
19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration 19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop
20 Chapter 20: Autopilot for Developers & Autopilot for Everyone
20.1 Autopilot for Developers: AI Assistance in Studio and Studio Web 20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI
21 Chapter 21: API Automation & Integration Service
21.1 Integration Service: Connectors, Connections & Connector Activities 21.2 API Workflows in Studio Web 21.3 HTTP Requests: Web APIs, the Orchestrator API & Connector Requests 21.4 Connector Builder: Custom Integration Service Connectors 21.5 Integration Service Event Triggers: Connected and Disconnected 21.6 GenAI Activities: Generative AI Inside Workflows
22 Chapter 22: Data Service, Context Grounding & Coded Workflows
22.1 Data Fabric (Data Service) Entities: Modeling Business Data 22.2 Data Fabric Activities and the Platform Connector 22.3 Context Grounding: Retrieval-Augmented Generation with Company Data 22.4 Coded Automations: Structure, Arguments & Invoking Workflows 22.5 Coded Automation Services: Orchestrator, UI Automation, Microsoft 365 & Custom Services
23 Chapter 23: Integrated Scenario Practice
23.1 Integrated Scenario Practice: Designing an End-to-End Solution
18.2 Running Local Triggers & the Event Inspection Tool
Key Takeaways Explain This Topic AI
Run Local Triggers starts all local triggers of the project in parallel through a generated TriggerEventArgs workflow.
Each trigger workflow receives a TriggerEventArgs argument with the trigger type, name, and target element or form details.
Stop Local Triggers cancels running trigger workflows while the main workflow continues.
Enable Local Trigger and Disable Local Trigger switch individual triggers on and off at run time.
The Event Inspection Tool (UI Explorer > Inspect Events) records native events such as Click, Key pressed, and Focus gained, with Clear and CSV export.
Last updated: September 2026
18.2 Running Local Triggers & the Event Inspection Tool
Core Concept: The exam description names "native event triggers: Run Local Triggers & Stop Local Triggers" and the Event Inspection Tool . Run and Stop Local Triggers control when an attended project listens for events, and the Event Inspection Tool shows which native events a UI element raises so you can configure an Application Event Trigger correctly.
Run Local Triggers
Run Local Triggers initializes and starts all local triggers of the project, that is, every trigger workflow listening for events on the user's machine.
Behind the scenes it generates a separate, read-only workflow named TriggerEventArgs at run time or while debugging. That workflow contains Trigger Scope activities that run all the project's triggers in parallel .
It can be used inside a workflow, or invoked from another workflow with Invoke Workflow File.
Activities placed after Run Local Triggers in the same workflow run only after the triggers stop.
The TriggerEventArgs argument
After the first run, each trigger workflow receives its own TriggerEventArgs argument with information about the event that fired it:
The trigger type and trigger name.
For user event triggers: the TargetElement that fired the trigger, with its Attributes , Selector , ImageBase64 (an image of the element), and DisplayDpiScaleFactor .
For form triggers: the FormSourceId and the form's Instance Name , plus the form components involved.
Use these values instead of searching the screen again, for example to read which row of a grid the user clicked.
Stop Local Triggers
Stop Local Triggers terminates the local triggers:
It cancels all ongoing actions , including workflows that triggers started and that are still running.
The activities of the main workflow continue as usual .
A typical design lets a "Close assistant" button on the side form call Stop Local Triggers, after which the main workflow saves its work and ends.
Enable and Disable Local Trigger
When many triggers are active, or when triggers only make sense at certain stages of the user's work, use:
Disable Local Trigger to pause one or more triggers that Run Local Triggers started.
Enable Local Trigger to activate them again, including triggers whose Enabled property was False at start.
Example: the "Submit claim" trigger is disabled until the "Check policy" workflow has passed, then enabled.
The Event Inspection Tool
Application Event Trigger needs an event type , and the available events depend on the element and its technology. A web element may expose different events than a Java or desktop element. The Event Inspection Tool shows which events the element really raises when the user interacts with it.
Opening and using it
Open UI Explorer , select a valid UI element, and select Inspect Events on the toolbar.
In the Event filter , choose the event types to monitor, such as Click , Key pressed , Focus gained , and Focus lost .
Start recording and interact with the element as the user would.
The Event list shows each captured event with its details.
Clear deletes the recorded events, and CSV exports them for analysis.
Then configure the Application Event Trigger with the event type you saw.
Native event families
Application Event Trigger supports native events from several technologies: WND (top-level windows), CTRL , JAVA , WEBCTRL , HTML , and UIA . For a top-level window, examples are Appeared , Disappeared , Title changed , State changed , and Location changed . Each event passes a matching argument type, such as TextChangedArgs for title changes or StateChangedArgs for state changes.
Application Event Trigger Settings Worth Knowing
- Setting Meaning
- Target The top-level window or element; only strict selectors, without anchors
- Event type Required; the list depends on the element
- Selectors Additional full selectors to monitor for the same event
Include children Also monitor the element's children (not for Appeared or Disappeared, and not for top-level windows)
- Match sync Synchronous selector matching, supported only for Java events other than Appeared and Disappeared
- Scheduling mode / Enabled As for other triggers
- Worked Example
A service desk agent should see customer details whenever they select a ticket row in a desktop ticketing tool.
With Inspect Events , the developer finds that selecting a row raises a State changed event on the row element, not a Click event on the grid.
The trigger workflow starts with an Application Event Trigger on the grid with Include children selected and the event type found in step 1, using Sequential Collapse so rapid row changes only process the latest selection.
The workflow reads the ticket ID from TriggerEventArgs and updates a side form with Set Form Values.
Troubleshooting Checklist
The trigger never fires: inspect the element's events with the Event Inspection Tool; the event you chose may not be raised by that element.
The trigger fires too often: narrow the target, turn off Include children , or use Sequential Collapse so bursts collapse into one run.
Workflows keep running after the user is done: call Stop Local Triggers from a close action.
A stage-specific trigger fires too early: start it with Enabled set to False and enable it later with Enable Local Trigger .