# Queues

When selecting a queue from the connection's panel, the main queue view will open up. Here you can get some overview of your queue, including metrics for the last processed jobs, as well as tables that shows the jobs in their different status.

![](/files/-MWP7tUP3CnPEKIgGoZE)

From this view it is possible to perform some queue-wide operations such as: adding new jobs, global **pause/resume** and queue **deletion**. Keep in mind that deletion is a destructive operation that cannot be undone.

![](/files/-MWP8oDLQETRe13ro8Xp)

The tables are not auto-updated so you will need to hit the refresh button in order to get the latest view of a given queue.

### Adding jobs

It is possible to add new jobs to a given queue. This is useful when trying out the workers in different contexts. In order to add a new job just press on the + icon in the queue bar:

![](/files/-MeOnzdmP4_RowonfqKb)

{% hint style="info" %}
You need at least version 1.15.0 of the Taskforce connector or a direct Redis connection for the Add job feature to be available.
{% endhint %}

Clicking on the icon will open the "Add job" dialog:

![](/files/-MeOoIueROWTcEpvHKAF)

You will be able to name your job and optionally change the delay or max. attempts settings. For the data portion of the job you get a nice JSON editor. Just fill in your data and click on "Add":

![](/files/-MeOpHjTbHg1CquWu0Ik)

The job will be added directly to the queue and if the queue has running workers it will be processed accordingly.

{% hint style="info" %}
Leaving the job name empty will produce a job with the special name \_\_*default\_\_* which in Bull v3 is the default name when not providing one.
{% endhint %}


---

# Agent Instructions: 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.taskforce.sh/connections/queues.md?ask=<question>
```

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.