Search: state

of the job event in the Center database Job State The status of the job. Insights only ingest terminal states (i.e. successful, stopped, and faulted) Start Time The time when execution of the job began

" %)((( Job State )))|(% style="width:890px" %)((( The status of the job. Insights only ingest terminal states (i.e. successful, stopped, and faulted) ))) |(% style="width:242px" %)((( Start Time

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

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

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

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

the preceding updates. Unless otherwise stated in our documentation, akaBot does not guarantee forward

the preceding updates. * Unless otherwise stated in our documentation, akaBot does not guarantee forward

, 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

state authorities, the bank, a Law firm, an auditor. This term of confidentiality obligations shall

contained. Unless stated otherwise, all the remedies provided for in this EULA shall be cumulative

by, competent state authorities, the bank, a Law firm, an auditor. This term of confidentiality obligations

contained. * Unless stated otherwise, all the remedies provided for in this EULA shall be cumulative