Search: state
Last modified by admin on 2022/04/24 04:58
Refine your search
Select a category and activate filters on the current results
Location
Last author
- 14admin
- 3VuNH54
- 2Giang Tran
- 2Ly Nguyen
- 1Nhan Nguyen
Creator
- 17admin
- 4Giang Tran
- 1Nhan Nguyen
Last modification date
Creation date
Object type
Uploaded by
- 16admin
- 6Nhan Nguyen
- 1Giang Tran
- 1VuNH54
Upload date
[8] Setting up Auto Login for Unattended Agent
Located in
- Rendered document content
, if there is more than one user session at a time, akaBot service mistakenly identifies that user's state as locked
- Raw document content
that user's state as locked or active. **Solution** : To allow 1 session for 1 user, please follow
[3] Review Document
Located in
- Rendered document content
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
- Raw document content
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
[1] About Data Service
Located in
[1] Product LifeCycle Support Terms
Located in
- Rendered document content
the preceding updates. Unless otherwise stated in our documentation, akaBot does not guarantee forward
- Raw document content
the preceding updates. * Unless otherwise stated in our documentation, akaBot does not guarantee forward
[4] Triggers
Located in
- Rendered document content
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
- Raw document content
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
[5] Trigger
Located in
- Rendered document content
: - 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
- Raw document content
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
[4] API resources
Located in
- Rendered document content
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
- Raw document content
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
[2] Workflow
Located in
- Rendered document content
, Name, State, Agent of the tasks. Users can also delete executed instances of this Workflow
- Raw document content
by ** Time, Name, State, Agent** of the tasks. [[image:image-20221028094515-7.png]] Users can also delete
[1] Agent
Located in
- Rendered document content
verification task states: PENDING: the verification task was created and waiting for verification from
- Raw document content
and can be logged in. There are three possible verification task states: * **PENDING
[1] Task
Located in
- Rendered document content
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
- Raw document content
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
next page »
Page
1
2
3
RSS feed for search on [state]