IP Library › Granted Patent US 12,189,510
Granted Patent B2
US 12,189,510 · App. 18/324,569 · Granted Jan 7, 2025

Long running workflows for robotic process automation

Inventors: Palak Kadakia (Redmond, WA); Liji J. Kunnath (Bangalore, IN); Amol Awate (Bangalore, IN); Remus Rusanu (Redmond, WA)
Assignee: UiPath, Inc.
G06F11/3476G06F9/45512G06F9/485G06F11/3495
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,189,510
App. No.
18/324,569
Filed
May 26, 2023
Granted
Jan 7, 2025
Kind
B2
Art Unit
2194
USPC
714/45
Abstract

Systems and methods for executing a robotic process automation (RPA) workflow are provided. The RPA workflow is executed by a first robot. The execution of the RPA workflow is suspended by the first robot. A current context of the RPA workflow is serialized at a time of the suspension and the current context of the RPA workflow is stored. The execution of the RPA workflow is resumed by a second robot based on a triggering condition by retrieving the current context of the RPA workflow. The first robot and the second robot may be the same robot or different robots.

Claims (83)

1. A computer-implemented method for executing a robotic process automation (RPA) workflow comprising:

transmitting, to a first robot, an indication to execute the RPA workflow;

transmitting, to the first robot, an indication to suspend the execution of the RPA workflow, wherein the execution of the RPA workflow is suspended by storing a current context of the RPA workflow at a time of the suspension; and

transmitting, to a second robot, an indication to resume the execution of the RPA workflow in response to a triggering condition, wherein the execution of the RPA workflow is resumed by retrieving the current context of the RPA workflow.

2. The computer-implemented method of claim 1 , wherein the triggering condition comprises completion of another RPA workflow.

3. The computer-implemented method of claim 1 , wherein the RPA workflow comprises a robot activity and a user activity.

4. The computer-implemented method of claim 3 , further comprising:

receiving, from the first robot, a user request requesting user input for the user activity from a user;

transmitting, to the user, the user request; and

receiving, from the user, user input in response to the user request,

wherein transmitting, to a second robot, an indication to resume the execution of the RPA workflow in response to a triggering condition comprises transmitting, to the second robot, the indication to resume the execution of the RPA workflow in response to receiving the user input.

5. The computer-implemented method of claim 3 , wherein the user activity comprises at least one of a validation activity or an approval activity.

6. The computer-implemented method of claim 1 , further comprising:

maintaining a log recording states of the RPA workflow.

7. The computer-implemented method of claim 1 , wherein the first robot and the second robot are the same robot.

8. The computer-implemented method of claim 1 , wherein the first robot and the second robot are different robots.

9. The computer-implemented method of claim 1 , wherein the transmitting, to the first robot, the indication to execute the RPA workflow, the transmitting, to the first robot, the indication to suspect the execution of the RPA workflow, and the transmitting, to the second robot, the indication to resume the execution of the RPA workflow are performed by an orchestrator implemented in a cloud computing system.

10. A system for executing a robotic process automation (RPA) workflow comprising:

a memory storing computer instructions; and

at least one processor configured to execute the computer instructions, the computer instructions configured to cause the at least one processor to perform operations of:

transmitting, to a first robot, an indication to execute the RPA workflow;

transmitting, to the first robot, an indication to suspend the execution of the RPA workflow, wherein the execution of the RPA workflow is suspended by storing a current context of the RPA workflow at a time of the suspension; and

transmitting, to a second robot, an indication to resume the execution of the RPA workflow in response to a triggering condition, wherein the execution of the RPA workflow is resumed by retrieving the current context of the RPA workflow.

11. The system of claim 10 , wherein the RPA workflow comprises a robot activity and a user activity.

12. The system of claim 11 , the operations further comprising:

receiving, from the first robot, a user request requesting user input for the user activity from a user;

transmitting, to the user, the user request; and

receiving, from the user, user input in response to the user request,

wherein transmitting, to a second robot, an indication to resume the execution of the RPA workflow in response to a triggering condition comprises transmitting, to the second robot, the indication to resume the execution of the RPA workflow in response to receiving the user input.

13. The system of claim 10 , wherein the first robot and the second robot are the same robot.

14. The system of claim 10 , wherein the first robot and the second robot are different robots.

15. The system of claim 10 , wherein the system is implemented in a cloud computing system.

16. A non-transitory computer-readable medium storing computer program instructions for executing a robotic process automation (RPA) workflow, the computer program instructions when executed by at least one processor cause the at least one processor to perform operations comprising:

transmitting, to a first robot, an indication to execute the RPA workflow;

transmitting, to the first robot, an indication to suspend the execution of the RPA workflow, wherein the execution of the RPA workflow is suspended by storing a current context of the RPA workflow at a time of the suspension; and

transmitting, to a second robot, an indication to resume the execution of the RPA workflow in response to a triggering condition, wherein the execution of the RPA workflow is resumed by retrieving the current context of the RPA workflow.

17. The non-transitory computer-readable medium of claim 16 , wherein the triggering condition comprises completion of another RPA workflow.

18. The non-transitory computer-readable medium of claim 16 , the operations further comprising:

maintaining a log recording states of the RPA workflow.

19. The non-transitory computer-readable medium of claim 16 , wherein the first robot and the second robot are the same robot.

20. The non-transitory computer-readable medium of claim 16 , wherein the first robot and the second robot are different robots.

21. The non-transitory computer-readable medium of claim 16 , wherein the at least one processor is implemented in one or more computing devices and the one or more computing devices are implemented in a cloud computing system.

22. A computer-implemented method for executing a robotic process automation (RPA) workflow comprising:

transmitting, from an orchestrator implemented in a cloud computing system to a first robot, an indication to execute the RPA workflow;

transmitting, from the orchestrator to the first robot, an indication to suspend the execution of the RPA workflow; and

transmitting, from the orchestrator to a second robot, an indication to resume the execution of the RPA workflow in response to a triggering condition.

23. The computer-implemented method of claim 22 , wherein the triggering condition comprises completion of another RPA workflow.

24. The computer-implemented method of claim 22 , wherein the RPA workflow comprises a robot activity and a user activity.

25. The computer-implemented method of claim 24 , further comprising:

receiving, from the first robot, a user request requesting user input for the user activity from a user;

transmitting, to the user, the user request; and

receiving, from the user, user input in response to the user request,

wherein transmitting, from the orchestrator to a second robot, an indication to resume the execution of the RPA workflow in response to a triggering condition comprises transmitting, from the orchestrator to the second robot, the indication to resume the execution of the RPA workflow in response to receiving the user input.

26. The computer-implemented method of claim 24 , wherein the user activity comprises at least one of a validation activity or an approval activity.

27. The computer-implemented method of claim 22 , further comprising:

maintaining a log recording states of the RPA workflow.

28. The computer-implemented method of claim 22 , wherein the first robot and the second robot are the same robot.

29. The computer-implemented method of claim 22 , wherein the first robot and the second robot are different robots.

30. A system for executing a robotic process automation (RPA) workflow comprising:

a memory storing computer instructions; and

at least one processor configured to execute the computer instructions, the computer instructions configured to cause the at least one processor to perform operations of:

transmitting, to a first robot, an indication to execute the RPA workflow;

transmitting, to the first robot, an indication to suspend the execution of the RPA workflow; and

transmitting, to a second robot, an indication to resume the execution of the RPA workflow in response to a triggering condition,

wherein the system is implemented in a cloud computing system.

31. The system of claim 30 , wherein the RPA workflow comprises a robot activity and a user activity.

32. The system of claim 31 , the operations further comprising:

receiving, from the first robot, a user request requesting user input for the user activity from a user;

transmitting, to the user, the user request; and

receiving, from the user, user input in response to the user request,

wherein transmitting, to a second robot, an indication to resume the execution of the RPA workflow in response to a triggering condition comprises transmitting, to the second robot, the indication to resume the execution of the RPA workflow in response to receiving the user input.

33. The system of claim 30 , wherein the first robot and the second robot are the same robot.

34. The system of claim 30 , wherein the first robot and the second robot are different robots.

35. A non-transitory computer-readable medium storing computer program instructions for executing a robotic process automation (RPA) workflow, the computer program instructions when executed by at least one processor cause the at least one processor to perform operations comprising:

transmitting, to a first robot, an indication to execute the RPA workflow;

transmitting, to the first robot, an indication to suspend the execution of the RPA workflow; and

transmitting, to a second robot, an indication to resume the execution of the RPA workflow in response to a triggering condition,

wherein the at least one processor is implemented in one or more computing devices and the one or more computing devices are implemented in a cloud computing system.

36. The non-transitory computer-readable medium of claim 35 , wherein the triggering condition comprises completion of another RPA workflow.

37. The non-transitory computer-readable medium of claim 35 , the operations further comprising:

maintaining a log recording states of the RPA workflow.

38. The non-transitory computer-readable medium of claim 35 , wherein the first robot and the second robot are the same robot.

39. The non-transitory computer-readable medium of claim 35 , wherein the first robot and the second robot are different robots.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 26, 2023
From: KADAKIA, PALAK; KUNNATH, LIJI J.; AWATE, AMOL; RUSANU, REMUS
To: UIPATH, INC.
Reel/Frame 063775/0363 →
Priority Claims (1)
IN 201911041916 · Oct 16, 2019 · national
Continuity (3)
Continuation 17658260 · Apr 7, 2022
Continuation 16716860 · Dec 17, 2019
Related Publication 20230297488A1 · Sep 21, 2023
References Cited (49)
US 8375389B2 · Allen · 2013 [cited by examiner]
US 9754231B2 · Channabasavaiah et al. · 2017 [cited by applicant]
US 10372508B2 · Hosabettu et al. · 2019 [cited by applicant]
US 10599722B1 · Ewing et al. · 2020 [cited by applicant]
US 11288557B2 · Gligan et al. · 2022 [cited by applicant]
US 11392477B2 · Dines · 2022 [cited by applicant]
US 20050147054A1 · Loo et al. · 2005 [cited by applicant]
US 20060279764A1 · Shimada · 2006 [cited by applicant]
US 20090196512A1 · Shelton et al. · 2009 [cited by applicant]
US 20100064357A1 · Baird et al. · 2010 [cited by applicant]
US 20170270431A1 · Hosabettu et al. · 2017 [cited by applicant]
US 20170352041A1 · Ramamurthy et al. · 2017 [cited by applicant]
US 20180074931A1 · Garcia et al. · 2018 [cited by applicant]
US 20180232204A1 · Ghatage et al. · 2018 [cited by applicant]
US 20180370033A1 · Geffen et al. · 2018 [cited by applicant]
US 20190066013A1 · Gupta et al. · 2019 [cited by applicant]
US 20190087395A1 · Priestas · 2019 [cited by examiner]
US 20190138596A1 · Singh · 2019 [cited by applicant]
US 20190147382A1 · Krishnamurthy · 2019 [cited by applicant]
US 20190155225A1 · Kothandaraman et al. · 2019 [cited by applicant]
US 20190205636A1 · Saraswat et al. · 2019 [cited by applicant]
US 20190286474A1 · Sturtivant · 2019 [cited by examiner]
US 20190286736A1 · Sturtivant · 2019 [cited by applicant]
US 20190354720A1 · Tucker et al. · 2019 [cited by applicant]
US 20200065334A1 · Rodriguez et al. · 2020 [cited by applicant]
US 20200073729A1 · Sturtivant et al. · 2020 [cited by applicant]
US 20200111023A1 · Pondicherry et al. · 2020 [cited by applicant]
US 20200134524A1 · Gentilhomme et al. · 2020 [cited by applicant]
US 20200180155A1 · Hall · 2020 [cited by applicant]
US 20200233707A1 · Ramamurthy et al. · 2020 [cited by applicant]
US 20200364404A1 · Priestas et al. · 2020 [cited by applicant]
US 20210200523A1 · Singh · 2021 [cited by applicant]
US 20210252704A1 · Hall · 2021 [cited by applicant]
US 20210258389A1 · Hall et al. · 2021 [cited by applicant]
EP 1256900A1 · 2002 [cited by applicant]
“Long Running Workflow—Human Interaction,” retrieved online on Aug. 30, 2019, at https://www.flexrule.com/process-automation/, 5 pgs. [cited by applicant]
“RPA—Robotics Automation Process,” retrieved online on Aug. 29, 2019, at https://www.flexrule.com/robotics/?q=/rpa/&, 4 pgs. [cited by applicant]
“Managed ROC—Robotic Operations Center,” Accelirate Inc., retrieved online on Aug. 29, 2019, at https://www.accelirate.com/wp-content/uploads/2019/01/Managed-ROC.pdf, 2 pgs. [cited by applicant]
“User Guide—Kryon Console v5.19,” Kryon Systems Ltd., retrieved online on Aug. 29, 2019, at https://us.v-cdn.net/6030908/uploads/editor/8h/t3jiixqx9712.pdf, 89 pgs. [cited by applicant]
“Understanding the RPA Monitor BOTs View,” retrieved online on Aug. 29, 2019, at https://jacada.zendesk.com/hc/en-us/articles/360001675452, 5 pgs. [cited by applicant]
“Pega Robot Manager,” Pegasystems, Inc., retrieved online on Sep. 9, 2019, at https://community.pega.com/marketplace/components/pega-robot-manager, 4 pgs. [cited by applicant]
“Intellibot RPA Platform,” Uber Techlabs, retrieved online on Sep. 9, 2019, at https://intellibot.io/, 10 pgs. [cited by applicant]
“Robotic Process Automation (RPA),” Nice Robotic Automation, retrieved online on Sep. 5, 2019, at https://www.nice.com/websites/rpa/robotic-automation.html. 7 pgs. [cited by applicant]
YouTube Video “Power Your Document Processes with RPA,” Kofax, Inc., uploaded on Nov. 8, 2018, initially retrieved online on Sep. 5, 2019, at https://www.youtube.com/watch?v=cvCxM2mYeCo, Digital Video, 1 pgs. [cited by applicant]
Non-Final Office Action mailed Jun. 19, 2020, in connection with U.S. Appl. No. 16/654,653, filed Oct. 16, 2019, 20 pgs. [cited by applicant]
Extended European Search Report mailed Feb. 18, 2021, in connection with European Patent Application No. 20196352.7, filed Sep. 16, 2020, 11 pgs. [cited by applicant]
Non-Final Office Action mailed Jun. 17, 2021, in connection with U.S. Appl. No. 17/075,726, filed Oct. 21, 2020, 43 pgs. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Nov. 24, 2021, in connection with U.S. Appl. No. 17/075,726, filed Oct. 21, 2020, 14 pgs. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Oct. 25, 2022 in connection with U.S. Appl. No. 17/649,558, filed Feb. 1, 2022, 12 pgs. [cited by applicant]