> For the complete documentation index, see [llms.txt](https://docs.jigx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jigx.com/building-apps-with-jigx/data/data-providers/rest/rest-error-handling/working-with-commandqueue.md).
# Working with commandQueue
## commandQueue table
The commandQueue is a system table, when a device is offline items are queued on the table. When the device comes online the items in the queue are processed. However, if items on the queue go into error, they are not processed and remain on the queue. Errors from REST methods, except for `action.sync-entity/entities` are queued in the commandQueue table. The commandQueue is exposed in Jigx Dev tools, allowing you to [debug](/building-apps-with-jigx/jigx-builder-code-editor/debugging.md) . You can expose the commandQueue table in a jig and then use the commandQueue actions to interact with the queued items that are in error state by either performing a retry or delete. Take note that when syncing an item or when the device is offline the `commandId` is not available.
commandQueue
### commandQueue actions (retry, delete, clear)
There are two actions related specifically to the commandQueue namely:
* `action.retry-queue-command` - executes a retry of the REST function called.
* `action.delete-queue-command` - Only deletes the item from the commandQueue. The record will still be saved locally on the device. You need to provide separately for the deleting of the local data, which can be achieved through an `action.sync-entity/entities` or executing a delete method on the local data provider.
* `action.clear-queue` - Use this action to clear commands from the queue for a specific id.
**Action configuration:**
```yaml
swipeable:
left:
- label: Delete
icon: close
color: negative
onPress:
type: action.delete-queue-command
options:
id: =@ctx.current.item.id
- label: Retry
icon: button-refresh-arrow
color: primary
onPress:
type: action.retry-queue-command
options:
id: =@ctx.current.item.id
- label: Clear
icon: button-refresh-arrow
color: warning
onPress:
type: action.clear-queue
options:
id: =@ctx.current.item.id
```
## Batch operations on queue items
### **How to reset multiple queue items at the same time**
When you have a list of commandQueue items to retry (not necessarily all failed items), send the selected item’s `id` from the datasource using `id: =@ctx.datasource.command-queue.id`.
If there are multiple `id` in the response, the action will run through each one in the array.
{% tabs %}
{% tab title="action" %}
```yaml
actions:
- numberOfVisibleActions: 1
children:
- type: action.retry-queue-command
options:
title: Retry all
id: =@ctx.datasources.command-queue.id
```
{% endtab %}
{% tab title="datasource" %}
```yaml
type: datasource.sqlite
options:
provider: DATA_PROVIDER_LOCAL
entities:
- _commandQueue
query: |
SELECT
id, queue, type, payload, state, error
FROM [_commandQueue]
ORDER BY id;
jsonProperties:
- payload
```
{% endtab %}
{% endtabs %}
## Considerations
* The `commandId` matches the `id` in the error table, this is important when you want to build a jig/UI to deal with the error.
* When using the commandQueue actions the commandQueue id (`commandId`) is required.
* Use the error table to build a jig/UI as there is more data logged to the table than the commandQueue.
commandId & error id
* Use the \_commandQueue table as a datasource in your solution. It behaves like a normal entity table with change events and updates.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.jigx.com/building-apps-with-jigx/data/data-providers/rest/rest-error-handling/working-with-commandqueue.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.