Skip to main content

How to monitor and cancel background jobs

When you'd do this: you've triggered an analysis, generation, or synthesis run and want to watch it progress — or you need to stop one that's running too long, was started by mistake, or is no longer needed because the artefact it's analysing has changed.

REQQA runs analysis, story/requirement generation, and synthesis as background jobs, so triggering one never makes you wait in the browser. The Job Queue page is where you watch all of them, across every job type, and where you can stop one directly.

Before you start​

  • You need an analysis, generation, or synthesis job already triggered — the Job Queue has nothing to show otherwise.
  • Cancellation is available to any authenticated member of your organisation; there's no separate permission to request.

Steps​

  1. Open Job Queue from the application hub. The page is split into two tables:
    • Active — everything currently queued or running, across analysis, generation and synthesis, with live progress, current step, and who started it.
    • Recent — the last 20 completed jobs, with their outcome (Finished, Partial, Failed, Cancelled, or Superseded) and, for analyses, the issue count.
  2. The page auto-refreshes every 10 seconds while anything is active, so you don't need to reload it by hand to watch progress.
  3. To cancel one job: find its row in the Active table and click Cancel. Confirm the prompt. The job is stopped immediately — dequeued if it hadn't started yet, signalled to halt mid-step if it had — and any partial results it had already written are marked Superseded in the same action.
  4. To cancel every active analysis for one artefact at once: if more than one analysis is active for the same requirement or story — this can happen if you triggered a bulk run and an individual one close together — a Cancel All notice appears above the Active table naming the artefact and the count. Click Cancel All, confirm, and every one of them is stopped together. If one of them can't be stopped for some reason, the confirmation result tells you which, by name, rather than failing silently.
  5. A cancelled job moves to the Recent table with status Cancelled. Don't confuse this with Superseded — that status means REQQA stopped the job automatically because you (or someone else) triggered a newer analysis against a revision the old job hadn't caught up to, not because anyone clicked Cancel.
note

You can't accidentally end up with two analyses racing each other for the same artefact and revision — REQQA rejects a duplicate trigger outright, and supersedes (rather than runs alongside) a trigger against a newer revision. Cancel and Cancel All exist for deliberately stopping work you've decided you don't want, not for resolving a conflict REQQA would otherwise have let happen.

Result​

Nothing is running that you didn't mean to still have running, and the Recent list gives you an honest record of what was explicitly stopped versus what was automatically superseded.