Search: 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

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

: - State: Status of task - Agent - Workflow Then choose a value in the “Equal box” dropdown list And Choose in the dropdown list: - State: Status of task - Agent - Workflow Then choose a value

in the dropdown list: - State: Status of task - Agent - Workflow Then choose a value in the “Equal box” dropdown list ))) |And|((( Choose in the dropdown list: - State: Status of task - Agent - Workflow

clean up queue items. Add an option for Trigger->Task->State condition to trigger task during specific

to frequently clean up queue items. * Add an option for Trigger->Task->State condition to trigger task during

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

, 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

verification task states: PENDING: the verification task was created and waiting for verification from

and can be logged in. There are three possible verification task states: * **PENDING

displays by default all the tasks that are running, and the ones placed in a pending state, regardless

for deployment purposes where the Agent is located. 6 State Current status of the tasks. Available statuses

, State of Tasks No Column /Label Description Type Maximum Input Requirement 1 Search box Search

in a pending state, regardless of whether they were started manually or through a schedule. On this page, you

is located. |6|State|Current status of the tasks. Available statuses are: FAULTED: the tasks have encountered

allows you to search a task list by Free search box, Agent Name, State of Tasks [[image:image

Before stating exploring all the main function of akaBot Center, please follow the instruction to install and Activate akaBot Center here. During the usage of akaBot Center, there are many instances where you need to input data to perform certain actions, such as Create/Edit or Filter for specific data

Before stating exploring all the main function of akaBot Center, please follow the instruction to install and Activate akaBot Center [[here>>http://devdocs.akabot.io/bin/view/akaBot%20Center/Center%20Installation/]]. During the usage of akaBot Center, there are many instances where you need to input data

] The queue automatically transitions to the Expired state even though it was previously in the Successfully state. 11. [Webhook] Not displaying all events in Subscribed Events. 12. [Report] Does not export

to the Expired state even though it was previously in the Successfully state. ~11. [Webhook] Not displaying all