docspell/website/site/content/docs/webapp/processing.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

43 lines
1.5 KiB
Markdown
Raw Normal View History

2020-07-27 20:13:22 +00:00
+++
2022-01-27 19:23:15 +00:00
title = "Job Queue"
2020-07-27 20:13:22 +00:00
weight = 80
[extra]
mktoc = true
+++
2022-01-27 19:23:15 +00:00
# Job Queue
2020-07-27 20:13:22 +00:00
The page *Processing Queue* shows the current state of document
processing for your uploads. The page currently only shows at most the
80 newest jobs. There is a maximum of 40 done jobs (successful,
cancelled or failed) and 40 not done jobs.
2020-07-27 20:13:22 +00:00
The sidebar lets you filter for a specific job state. The *Currently
Running* tab shows all jobs that are currently executing and their log
output. The page refreshes automatically to show the progress.
2020-07-27 20:13:22 +00:00
Example screenshot:
{{ figure(file="processing-queue.png") }}
2020-07-27 20:13:22 +00:00
You can cancel running jobs or remove waiting ones from the queue. If
you click on the small file symbol on finished jobs, you can inspect
its log messages again. A running job displays the job executor id
that executes the job.
The jobs listed here are all long-running tasks for your collective.
Most of the time it executes the document processing tasks. But user
defined tasks, like "import mailbox", are also visible here.
Since job executors are shared among all collectives, it may happen
that a job is some time waiting until it is picked up by a job
executor. You can always start more job executors to help out.
If a job fails it first enters "stuck" state and is retried after some
time. Only if it fails too often (can be configured), it then is
finished with *failed* state.
2020-07-27 20:13:22 +00:00
For the document-processing task, if processing finally fails or a job
is cancelled, the item is still created, just without suggestions.