orchestrator

latest

false

Getting started
- Introduction
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Time-to-live Periods
- Orchestrator Outbound IP Addresses
- Notifications
Best practices
- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Folders
- Monitoring
- Access control
- Configuring automation capabilities
  - Enabling personal automations
    - Enabling individual users to run personal automations
- Machines
- Packages
- Audit
- Credential Stores
  - Integrating credential stores
  - Managing credential stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Settings
  - Robot Security Tab
  - Scalability Tab
    - SignalR (Robots)
Cloud robots
- Automation Cloud™ Robots - VM
- Configuring VPN for cloud robots
- My notifications
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Process Data Retention Policy
Apps
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
Triggers
- About triggers
- Managing triggers
- Managing Non-Working Days
- Using Cron Expressions
  - Triggering jobs on the last day of the month
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
Queues
- About Queues and Transactions
- Bulk uploading Queue Items using a CSV file
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
Test Suite - Orchestrator
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
- Testing Data Retention Policy
Resource Catalog Service
- About Resource Catalog Service
Authentication
- About Authentication
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
- Environments
  - Managing Environments
- Jobs
- Triggers
- Monitoring
  - Robots
- Resources
Troubleshooting
- About Troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator User Guide

DELIVERY:

DELIVERY:

Automation Cloud Automation Cloud Public Sector Automation Suite Standalone

Last updated Nov 20, 2024

Running Personal Remote Automations

This article walks RPA developers, citizen developers, and business users through the steps for running personal automations from Orchestrator by manually launching a job via the Start Job functionality or by using a trigger.

Prerequisites:

You or an administrator previously deployed the background process you want to execute to a folder you have access to.
An administrator allocated the unattended infrastructure for running jobs by adding a machine template object to the folder.

Start a Job as Yourself

Navigate to Automations > Jobs in the folder the background process resides in.
Click Start. The Start Job window is displayed.
From the Process Name drop-down, select the process you want to execute.
From the Account drop-down, select Run as Myself (Personal automation) to execute the job under your own identity. Note that this option is available only for background processes.
Configure the other settings following the instructions provided in the Starting a job documentation.
Click Start to start the job. The job is displayed as Pending on the Jobs page until a robot is available to pick it up.

Configure a Trigger to Launch Jobs as Yourself

Navigate to Automations > Triggers in the folder the background process resides in.
Click Add a new trigger. The Create trigger window is displayed.
On the Name field, give your trigger a meaningful name.
From the Process Name drop-down, select the process you want that trigger to launch jobs for.
From the Account drop-down, select Run as Myself (Personal automation) to execute the jobs launched by the trigger under your own identity. Note that this option is available only for background processes.
Configure the other settings following the instructions provided in the Managing triggers documentation.
Click Add to add the trigger. The trigger is displayed in the Triggers page and will launch a job under your own identity according to the trigger configuration.

On this page

Start a Job as Yourself
Configure a Trigger to Launch Jobs as Yourself

Was this page helpful?

PREVIOUSWorking with long-running workflows

NEXTProcess Data Retention Policy

Support and Services

Get The Help You Need

Learning RPA - Automation Courses

UiPath Community Forum

Trust and Security

© 2005-2024 UiPath. All rights reserved.