Skip to content
When the chain does not run, and how you find out

When the chain does not run, and how you find out

Finalise: what the button starts, and what it writes · presentation 5 of 5 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Finalise: what the button starts, and what it writes · presentation 5 of 5

When the chain does not run, and how you find out

You can tell the difference between a posting that has not happened yet, one that failed and will never be retried…

Claimed, not reserved

Step 1 — Know that a claimed job is gone from the queue

You will know why "it will retry" is usually wrong.

What this step names
  1. If the handler then throws
  2. There is no row left to retry…
  3. Carrying the event code
  4. The properties that name your document
  5. The message

Step 2 — Know what the sweeper does cover

You will know why the design is still safe.

What this step names
  1. A background tick reads up to ten rows still waiting in the…
  2. In priority order across the kinds of job it sweeps
  3. Calls the job endpoint once for each row…

Step 3 — Know that a backlog is a real, measurable state

You will recognise a third possibility.

Where this step sits
    flowchart TD
  s1["1. Know that a claimed job is…"]
  s2["2. Know what the sweeper does cover"]
  s3["3. Know that a backlog is a…"]
  s4["4. Know which failures to expect…"]
  s5["5. Run the check, in this order"]
  s6["6. Know what VOID does…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;
  

What actually fails

Step 4 — Know which failures to expect, and why

You will stop treating a failed posting as exotic.

What this step names
  1. The causes to check first are mapping
  2. Not machinery: a receivable account that is not mapped in the company…
  3. A settlement method with no cashbook or GL code
  4. A sales
  5. Tax line that resolved no account on a document whose customer has…

Step 5 — Run the check, in this order

You will have a routine that takes half a minute.

  • Open Trace Document under Error Checking
  • Press Resolve: if the cause is still there…
Screen capture pending the demo tenant

Financial Report, Error Checking, Trace Document, showing the Missing Journal check for a FINAL document

Step 6 — Know what VOID does, and what it cannot undo

You will know the way back.

Where this step sits
    flowchart TD
  s1["1. Know that a claimed job is…"]
  s2["2. Know what the sweeper does cover"]
  s3["3. Know that a backlog is a…"]
  s4["4. Know which failures to expect…"]
  s5["5. Run the check, in this order"]
  s6["6. Know what VOID does…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s6 here;
  

NarrationSlide 1 of 9

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.

Last updated on