{"componentChunkName":"component---src-templates-default-template-tsx","path":"/documentation/concepts/task_states/","result":{"data":{"asciidoc":{"id":"01343e8d-6b5c-5092-8213-bb5ebba10c92","html":"
\n
Table of Contents
\n\n
\n
\n

Task States

\n
\n
\n

Automation in HIRO™ is task-centric. Therefore, Automation Tasks are the\ncentral data objects to trigger the HIRO™ Engine. Automation Tasks have a\nlifecycle - they are created, processed and finally either succeed or fail.\nThe following diagram illustrates the state machine of Automation Task status.

\n
\n
\n
\n\"Task\n
\n
Figure 1. Task State Diagram
\n
\n
\n

The black lines indicate transitions performed by the Engine, whereas:

\n
\n
\n
    \n
  • \n

    some transitions will be triggered only be Engine’s internal task handling

    \n
    • \n
  • \n

    some transitions can be triggered by special KI language commands

    \n
    • \n
\n
\n
\n

The transitions marked in red may be performed from the outside, i.e. by connectors\nor other applications.

\n
\n
\n
\n
NEW
\n
\n

New task which is ready to be processed by the HIRO™ Engine

\n
\n

For compatibility reasons a missing status value is interpreted as NEW

\n
\n
\n
PROCESSING
\n
\n

Engine is currently working on this task to resolve it.

\n
\n
RESOLVED
\n
\n

Task processing has finished successfully. Technically that means: through\napplication of KIs all ToDo variables have been deleted.

\n
\n

This is a final state.

\n
\n
\n
WAITING
\n
\n

Task processing was suspended to wait for some external event (e.g. user approval).\nA task in that state must be set back to PROCESSING from the outside (by the\ncontrolling connector or other application).

\n
\n
STOPPED
\n
\n

Task processing has been stopped. In most cases this status means the Engine ran\nout of applicable knowledge.

\n
\n

This is a final state.

\n
\n
\n
TERMINATED
\n
\n

Task processing has been forcefully terminated. This could be triggered internally\nby some error conditions (see below) or externally (e.g. Connector/CLI).

\n
\n

This is a final state.

\n
\n
\n
\n
\n
\n
\n
\n

Typical state transitions triggered by the HIRO™ Engine

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
From stateTo stateTrigger

NEW

PROCESSING

successfully loaded task for processing

PROCESSING

RESOLVED

no remaining todo variable in task

PROCESSING

WAITING

KI command eject_issue

PROCESSING

STOPPED

KI command stop_issue

NEW / PROCESSING

TERMINATED

Processing node does not exist or is not accessible

\n
\n\n\n\n\n\n
\n\n\n
\n

The Engine writes the reason of a status change into the\nogit/Automation/deployStatus attribute. You might want to check this attribute\nto understand e.g. why tasks have been terminated.

\n
\n
\n
\n
\n
\n
\n

Which status changes can be triggered externally?

\n
\n
\n

The transitions listed below are allowed to be triggered by connectors or other\napplications:

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
From stateTo stateTrigger/Reason

PROCESSING

TERMINATED

External application (e.g. connector) decides then Engine\nshould not process that task anymore.

WAITING

TERMINATED

External application (e.g. connector) decides then Engine\nshould not process that task anymore

PROCESSING

WAITING

External application decides that Engine should (temporarily)\n pause processing that task (e.g. waiting for a user approval)

WAITING

PROCESSING

External application decides that a task processing can now\ncontinue

\n
\n
\n
\n

Relation to Knowledge Acquisition

\n
\n
\n

When a task status is STOPPED, this means that there was not sufficient knowledge\nto solve it. That’s why any task being in status STOPPED is a candidate for a\nnew knowledge acquisition session, and will be listed in the Task List in HIRO™.\nThe responsible Subject Matter Expert should teach the system how this task can be\nsolved the next time.

\n
\n
\n
","document":{"main":"Automation Task Lifecycle","title":"Automation Task Lifecycle","subtitle":""},"fields":{"toc":true,"location":["documentation","concepts","task_states"]}},"sidebarYaml":{"id":"6d066bdd-c982-5a69-b909-a31e6fc044e0","showIndex":null}},"pageContext":{"id":"01343e8d-6b5c-5092-8213-bb5ebba10c92","parent":"documentation"}},"staticQueryHashes":["1010459453","1010459453","2356112386","2356112386","2603905930","2603905930","3026652197","3026652197","3167850324","3167850324","63159454","63159454"]}