ActivityStateOverviewType (Complex Type)

Items

• identifier

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Display order:

  Identifier of the activity.

• realizationState

  Flags: RAM,runtime,AVals:2

  Multiplicity: [0,1]

  Display order:

  State of the activity processing: null (not started), in progress, complete.

• resultStatus

  Flags: RAM,runtime,AVals:8

  Multiplicity: [0,1]

  Display order:

  Operation result status of this activity run. If an activity realization is in progress (all tasks being run, or some of them stopped, or even all of the tasks stopped - but with work not being complete), here is either IN_PROGRESS (if there are no known errors, or if the activity handler does not report them), or PARTIAL_ERROR or FATAL_ERROR (if there are known errors, either partial or fatal). In a situations where the processing is stopped because of some fatal error (e.g. a "master" query cannot be issued against a resource in a synchronization activity, or a threshold was reached, etc.), usually FATAL_ERROR is present here. (Not IN_PROGRESS, although the activity - technically speaking - did not finish yet.) After the realization is complete, the status can no longer be IN_PROGRESS. It is usually either SUCCESS, PARTIAL_ERROR, or FATAL_ERROR. Other states (WARNING, HANDLED_ERROR) are possible but uncommon. For a distributed activity here is the aggregated result covering the whole activity. (May or may not be a simple aggregation of individual workers' results. For example, the result can be determined by taking into account success/failure status of items processed.) For a delegated activity here is the result of the delegate run (not the delegating one). For a simple (non-distributed, non-delegated) activity the result stored here is related to the result in the "task" field. However, there can be situations where this result is IN_PROGRESS, but the result in the "task" field is not IN_PROGRESS (because the activity run stopped). In any case, these results should not contradict each other.

• bucketProgress

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Display order:

  Activity progress in the terms of buckets.

• task

  Flags: RAM,runtime

  Multiplicity: [0,-1]

  Display order:

  Information about activity run within a task or tasks. However, not all runs are represented here: Delegating and distributing runs are not mentioned. Only local ones have their representation here.

• progressInformationVisibility

  Flags: RAM,runtime,AVals:2

  Multiplicity: [0,1]

  Display order:

  Is progress information hidden e.g. because of redundancy (if the activity runs directly in the root task)?

• persistence

  Flags: RAM,runtime,AVals:3

  Multiplicity: [0,1]

  Display order:

  How much is this state information persistent (between individual realizations)?

• activity

  Flags: RAM,runtime

  Multiplicity: [0,-1]

  Display order:

  State overview of child activities.