Search: state

, Add activity # Item Description More Details 1 New Create new sequence, flowchart, State Machine

to another without cluttering your project. State Machines – suitable for very large projects which have number of states triggered by a transition condition. In this item, you can create new these three types

|Create new sequence, flowchart, State Machine|2.2.1 New |2|Save|Save project|2.2.2 Save |3|Start|Run BOT

without cluttering your project. * State Machines – suitable for very large projects which have number of states triggered by a transition condition. In this item, you can create new these three types

stated in Article 3.1 above, at the time of collecting Customer's Personal Data or before commencing

or political opinions. 5.3. Data related to websites or applications: technical data (as stated above

such as auditors, lawyers, etc. in accordance with the law; (h) Courts, competent state agencies in accordance

stated in Article 3.1 above, at the time of collecting Customer's Personal Data or before commencing

(as stated above, including device type, operating system, browser type, browser settings, IP address

with the law; (h) Courts, competent state agencies in accordance with the provisions of law and/or as required

, Name, State, Agent of the tasks. Users can also delete executed instances of this Workflow

by ** Time, Name, State, Agent** of the tasks. [[image:image-20221028094515-7.png]] Users can also delete

duration in seconds to minutes. Success Rate Input Displays the percentage of jobs with state

to minutes. ))) |((( **Success Rate** )))|((( Input )))|((( Displays the percentage of jobs with state

Description id Integer jobKey String state JobState startTime DateTime endTime DateTime source

]| == (% style="color:#000000" %)**8. Job**(%%) == |Name|Type|Description |id|Integer| |jobKey|String| |state

The total number of tasks, including retried tasks, for each state: Successful Abandoned Failed Task

)))|((( The total number of tasks, including retried tasks, for each state: * **Successful** * **Abandoned

successfully processed document will still pass through a TOREVIEW state. If you have enabled automation, the document will pass through this state without the need for human verification. If you don’t have automation enabled for the pipeline, the document will have the TOREVIEW state until a human validator review

successfully processed document will still pass through a TOREVIEW state. If you have enabled automation, the document will pass through this state without the need for human verification. If you don’t have automation enabled for the pipeline, the document will have the TOREVIEW state until a human validator review

, if there is more than one user session at a time, akaBot service mistakenly identifies that user's state as locked

, akaBot service mistakenly identifies that user's state as locked or active. [[image:https

state for each Agent based on the input parameters and notifies the respective Agents about the pending

Integer False Agent Group ID robotId Integer False scheduleId Integer False state String False (PENDING, RUNNING, STOPPED, FAULTED, SUCCESSFUL). Supported multiple states, separated by commas page

state for each Agent based on the input parameters and notifies the respective Agents about the pending

|Integer|False|Agent Group ID |robotId|Integer|False| |scheduleId|Integer|False| |state|String|False|((( (PENDING, RUNNING, STOPPED, FAULTED, SUCCESSFUL). Supported multiple states, separated by commas ))) |page

was successfully launched, in which case it shows the word Successful in the State column. NOTE: The Successful state only indicates that the job was successfully launched. It does not reflect whether the job was successfully executed to the end or not. IMPORTANT: In case a job fails to start, its State will appear

launched, in which case it shows the word **Successful** in the **State** column. NOTE: The **Successful** state only indicates that the job was successfully launched. It does not reflect whether the job was successfully executed to the end or not. IMPORTANT: In case a job fails to start, its **State** will appear