Background Processing
Nama does a great deal of work behind you. Saving an invoice hands you the screen back immediately and writes its accounting entry a moment later; approving a document sends the email afterwards; a payroll rebuild is queued rather than made to happen while you wait.
That is what keeps the system quick, and it is also why work can occasionally go missing without anyone being told. A document can be saved and correct while its accounting effect failed. A notification can be raised and never sent. These are the screens where that becomes visible, and they are the first place to look whenever the answer to "but I saved it" is "yes, you did".
Each queue below is separate, with its own screen, its own worker and its own rules about retrying.
Which queue am I looking for?
| The complaint | The screen |
|---|---|
| "The invoice is saved but it is not in the ledger." | Business Requests |
| "Stock did not move." | Business Requests |
| "The approval email never arrived." | Pending Tasks |
| "The customer got no SMS." | Pending Tasks |
| "The salary sheet did not rebuild." | System Actions |
| "The system is slow and I do not know what it is doing." | Report Monitoring |
| "One slow job is holding up all the others." | Task Queues |
The one queue not covered here is the task scheduler, which runs jobs on a timer and keeps its own execution log — see Scheduled Tasks. How its work, and deferred entity flows, can be split into parallel lanes is covered in Task Queues.