Background jobs
Admin → Background Jobs. Automated tasks BMS runs without user input — scheduled imports, index updates, billing cycles, the nightly journals.
Columns
| Column | Description |
|---|---|
| Description | What the job does |
| User | The admin or system account that triggered it |
| Result | Outcome of the last run |
| Log | Link to the detail log |
| Errors / Warnings | Counts from the last run |
| Progress | Completion percentage |
| Status | Queued, Working, Completed or Failed |
| Queued / Completed | When it entered the queue, and when it finished |
Statuses
| Status | Meaning |
|---|---|
| Queued | Waiting behind other jobs |
| Working | Running now |
| Completed | Finished successfully |
| Failed | Errored and did not complete |
Reading the queue
Most jobs finish quickly. A long list of Queued or Working jobs is normal during a billing run, a nightly import, or after a bulk data change — the queue clears once processing is done. It is not by itself a sign of a problem.
When a job fails
A Failed status or a non-zero Errors count is worth opening the log for. The usual causes:
- Validation errors in an import file
- A third-party service temporarily unavailable — Xero, or the mail provider
- A configuration problem in whatever triggered the job
Most failed jobs can be re-triggered once the underlying cause is fixed. A job that fails repeatedly with nothing useful in the log is one to escalate.
Note
The nightly Cost of Sales journals run here. If a journal has not reached Xero, this queue is where to look before assuming the Xero connection is at fault — see Accounting for stock and cost of goods.