Hi @Product
We have a wrkflow that was launched with high priority, uses vision and loops, and experienced an 18 minute delay in completion of a section.
The usual processing time is about a minute and the failed job has been reset to meet SLAs.
It possible that the delay in activity contributes to unexpected behavior (i.e Are you there modal, timeout, AWS disconnections). (investigation ongoing)
As for large scheduled wrkflows, in another account there is one that starts at 7 but it's set to normal priority.
Is this a situation where I should modify the loop so less data is being processed?
Example of Usual Execution Speed
Start: WA-39: Click and fill an element using Vision RPA
Execution ID: 80b08ec5-833b-47de-854a-3c38cc6b576d
Time: 7:00:03 AM
End: WA-39: Click and fill an element using Vision RPA
Execution ID: eafae59c-168d-427c-98a9-7b15c6af7984
Time: 7:01:11 AM
Execution Delay Example
Start: WA-39: Click and fill an element using Vision RPA
Execution ID: eafae59c-168d-427c-98a9-7b15c6af7984
Time: 7:01:11 AM
End: WA-39: Click and fill an element using Vision RPA
Execution ID: 973f5765-8557-464f-9330-a5d2b9d8b4e3
Time: 7:19:58 AM
Launch ID: 1075302
Account name: 5812
Wrkflow: AWS 05: BMO_RTND_CHK (ID: 51979)
Launch name: Launch-1614320d
High Priority
Example from Another Account & Wkflow
Start: WA-41 Delay Wrk Action (1 min)
Execution ID: 3061bb5b-a747-442f-a28f-e28d85f27d99
Start Time: 7:11:58 AM
End Time: 7:50:44 AM
Impact: Unable to download file from web browser in next WA
Launch ID: 1072735
Account name: 5694
Wrkflow: Nursys V2 (ID: 48815)
Launch name: User:210047|ReqID:1386846
Normal Priority
