Work items move through states such as Data error, New, On hold, Active, Completed, Failed, and Unknown. The actions available for each work item depend on its current state.
Work item status
You can create work items in bulk by uploading them through a CSV file or by using the REST API. When you upload a large number of work items using a CSV file, they are inserted in multiple batches and the state of newly inserted work items is marked as draft until all of them are inserted from the file.
Work items progress through the following states:
- Data error: When work items have invalid data (while inserting from a CSV file), they are marked as Data error.
- New: When all the work items are inserted successfully, the work item state is marked as New.
- On hold: To defer processing, mark the work item as On hold.
- Active: When a work item is being processed by a device, the state is changed to Active.
- Completed: When a work item is processed successfully, the state is marked as Completed.
- Failed: When a work item fails during processing, the state is marked as Failed.
- Unknown: When a device fails to report back on the state of work item processing, it is marked as Unknown.
Status and applicable actions
In Workload Management (WLM), each work item progresses through states during its lifecycle. The actions you can perform on a work item depend on its current state. The following table describes each state and its available actions:
| Work item state | Description | Actions |
|---|---|---|
| Data Error | Data type mismatch when adding Work Items to the queue | View, Edit, and Delete |
| New | New Work Item is added | View, Edit, and Delete |
| On hold | Work Item is deferred for use by the queue administrator | View, Edit, and Delete |
| Active | Work Item is currently being processed | View and Edit |
| Completed | Work Item successfully processed by a device | View and Delete |
| Failed | Work Item processing has failed to execute on unattended devices | View, Edit, and Delete |
| Unknown | Work Items that are not identified by any of the devices | View, Edit, and Delete |
Other resources
- WLM - Queued work items in "Ready to Run" status are not getting deployed (A-People login required)
- WLM work item is not getting executed (A-People login required)
- A360 | WLM bots gets queued on same machine with Active status (A-People login required)
- A360 | Workitems are getting stuck in the Active status however WLM Automation's are not deployed on Runner Machines (A-People login required)
- A360.x | WLM | Task is getting stuck in "Ready to Run" status (A-People login required)