All help articles

Fixing refused records (To fix)

When the server refuses a record from a device, it waits under To fix. Check it, apply it again, or dismiss it with a note.

What this is for

A device records offline and sends later. Sometimes the server cannot accept what arrives. For example, a log code is already on another truck, or the record names a tree the lot does not have. Nothing is lost: the record is kept, and it waits under To fix until someone settles it.

The crew also sees it on their device, as ⚠ 1 to fix.

Where to find it

Records → To fix, or Review on the Today page.

At the top, Waiting, by reason shows a card per reason with a count. Click a card to show only those records. Below, Records lists every refused record, newest first. Filter by Show (Waiting, Settled, All), Reason and Lot.

Owners and managers can settle records. Auditors can read them.

Steps

  1. Click a record. Its page shows:
    • What happened: the reason in plain words, and what to do.
    • The record, its lot, who recorded it, on which device, and when.
    • What the device was told.
    • What the device sent, and The record now: how it stands today.
  2. Decide:
    • Check and apply again… when the record is right and should count.
    • Dismiss… when it should not count, or was recorded again correctly.

Check and apply again

  1. Click Check and apply again….
  2. Under Apply it to, keep The record it named, or, for a wrong tree, choose Another tree. Type the Tree label or tag, click Find tree, and pick the tree.
  3. Click Check what will change. Nothing is recorded yet. You see either It would be accepted now, with what will change, or It would be refused again, with the reason.
  4. If it would be accepted, add a note if you like and click Apply again.

The record is applied in your name, on your authority, dated when it happened on the device.

Dismiss

  1. Click Dismiss….
  2. Type a Note: why it can be left as it is. The note is required.
  3. Click Dismiss.

Nothing is recorded or changed. The record stays refused, and the device stops listing it as waiting.

Common reasons

ReasonWhat to do
A log already on another loadThe page links to the load that holds the code. If the code is there by mistake, take it off that load (Edit load…), then apply this one again. Otherwise dismiss.
A tree the organization does not haveOften a number typed wrong. Apply it again under the right tree, or dismiss.
A log code under the wrong treeOften a misread tag. Apply it again under the right tree, or dismiss.
Filed under the wrong lotApply it again under the right tree, or dismiss.
The record was deletedA change to a record that was deleted on another device. Dismiss. If it is still needed, have it recorded again as new.
What it was first saved as cannot changeSomeone tried to change a load's driver, plate or date. Delete the load and record it again with the right details, then dismiss this one.
The account was not allowed to record thisCheck it. A manager or owner can apply it again on their own authority, or dismiss.
The record did not pass the checksSomething was missing or out of range. Check what will change; if it is refused again, dismiss and have it recorded again correctly.

Every reason has its own explanation on the record's page.

Tips

  • Settle refused records soon. The crew sees them on their device until you do.
  • A note helps whoever reads it later, such as an auditor. Say what you saw and why you decided.
  • Settled records stay visible under Show → Settled, with who settled them and how.
  • Many records refused at once, for the same reason, usually have one cause, such as a lot that was voided. Fix the cause first.

Still stuck?

Write to support@tomruq.com. Say which page you were on and what you expected to see. Never send a password, a PIN or a reset code.