# US 2025/0094322 A1 · Fallback engine for updating selectors of an automation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0094322 A1
- Document ID: US20250094322A1
- Status: Published application
- Kind: A1
- Application number: 18/467,446
- Filed: 2023-09-14
- Published: 2025-03-20
- Earliest claimed: 2023-09-14
- Assignees: UiPath, Inc.
- Applicants: UiPath, Inc.
- Inventors: Gerd WEISHAAR
- Web page: https://patentgrep.com/patent/US20250094322A1

## CPC

- G06F 11/368: {for test version control, e.g. updating test cases to a new software version}
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F 11/3409: {for performance assessment}
- G06F 11/3466: {Performance evaluation by tracing or monitoring}
- G06F 11/3692: {for test results analysis}
- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method executed by a fallback engine is provided. The fallback engine is implemented as a computer program within a computing system. The method includes tracking information for versions for a selector stored in a selector repository. The information includes a proof of work defining an amount of use per version of the versions. The method includes determining a current state of an original selector version of the selector utilized by an automation and automatically implementing a fallback operation that updates a target of the selector of the automation from the original selector version to a different selector version based the proof of work for the different selector version in the selector repository.

## Claims

### Claim 1

A method executed by a fallback engine implemented as a computer program within a computing system, the method comprising:
tracking, by the fallback engine, information for one or more versions for a selector stored in a selector repository, wherein the information comprises a proof of work defining an amount of use per version of the one or more versions;
determining, by the fallback engine, a current state of an original selector version of the selector utilized by an automation; and
automatically implementing, by the fallback engine, a fallback operation that updates a target of the selector of the automation from the original selector version to a different selector version based the proof of work for the different selector version in the selector repository.

### Claim 2 (depends on 1)

The method of claim 1, wherein the fallback engine comprises an object browser configured to browse through f the selector repository.

### Claim 3 (depends on 1)

The method of claim 1, wherein the selector repository receives the selector and the one or more versions as contributions from one or more user devices and stores the selector and the one or more versions.

### Claim 4 (depends on 1)

The method of claim 1, wherein the information comprises the proof of work and probability, last-usage, or last-updated on a per version basis.

### Claim 5 (depends on 1)

The method of claim 1, wherein the proof of work comprises a hit count that defines the amount of use via an incrementing numerical value.

### Claim 6 (depends on 1)

The method of claim 1, wherein the current state comprises operable, inoperable, out-of-date, and out-of-use, or pointer error.

### Claim 7 (depends on 1)

The method of claim 1, wherein the fallback engine determines the current state of the selector of the automation based on an alert issued when the automation fails by a user device executing the automation.

### Claim 8 (depends on 1)

The method of claim 1, wherein the different selector version is a next best selector version comprising a highest value for a proof of work from the one or more versions in a selector repository.

### Claim 9 (depends on 1)

The method of claim 1, wherein the fallback engine tracks changes in the selectors and analyzes the information for one or more versions to determine the different selector version.

### Claim 10 (depends on 1)

The method of claim 1, wherein the automation comprises a test automation or a robotic process automation.

### Claim 11

A computer system comprising at least one processor executing computer program code for a fallback engine to cause the computer system to perform operations comprising:
tracking, by the fallback engine, information for one or more versions for a selector stored in a selector repository, wherein the information comprises a proof of work defining an amount of use per version of the one or more versions;
determining, by the fallback engine, a current state of an original selector version of the selector utilized by an automation; and
automatically implementing, by the fallback engine, a fallback operation that updates a target of the selector of the automation from the original selector version to a different selector version based the proof of work for the different selector version in the selector repository.

### Claim 12 (depends on 11)

The computer system of claim 11, wherein the fallback engine comprises an object browser configured to browse through f the selector repository.

### Claim 13 (depends on 11)

The computer system of claim 11, wherein the selector repository receives the selector and the one or more versions as contributions from one or more user devices and stores the selector and the one or more versions.

### Claim 14 (depends on 11)

The computer system of claim 11, wherein the information comprises the proof of work and probability, last-usage, or last-updated on a per version basis.

### Claim 15 (depends on 11)

The computer system of claim 11, wherein the proof of work comprises a hit count that defines the amount of use via an incrementing numerical value.

### Claim 16 (depends on 11)

The computer system of claim 11, wherein the current state comprises operable, inoperable, out-of-date, and out-of-use, or pointer error.

### Claim 17 (depends on 11)

The computer system of claim 11, wherein the fallback engine determines the current state of the selector of the automation based on an alert issued when the automation fails by a user device executing the automation.

### Claim 18 (depends on 11)

The computer system of claim 11, wherein the different selector version is a next best selector version comprising a highest value for a proof of work from the one or more versions in a selector repository.

### Claim 19 (depends on 11)

The computer system of claim 11, wherein the fallback engine tracks changes in the selectors and analyzes the information for one or more versions to determine the different selector version.

### Claim 20 (depends on 11)

The computer system of claim 11, wherein the automation comprises a test automation or a robotic process automation.
