Skip to content
waputuGet started
← Back to support and search

Inventory

Read freshness and investigate stale inventory

Understand source age, scheduled reads and failed synchronization.

For all users; owners/admins for connection changes · Reviewed September 9, 2026

Before you start

  • Identify the specific facility and report you are reviewing.
  • Do not assume a recent page refresh means a recent state read.

Where to click

  1. 1Home
  2. 2Freshness chip
  3. 3State connection
  4. 4Refresh
  5. 5Sublot review
Illustrated navigation sequence. Exact controls appear in the numbered instructions below.

Step-by-step instructions

  1. 1Home

    Read the facility freshness chip and run times. Inventory, rooms and events can have different last-run times.

  2. 2Freshness chip

    Open the linked connection or help page. Distinguish a stale successful result from a failed run.

  3. 3State connection

    An owner or admin should check token status and facility run times. Keep source age separate from the configured schedule.

  4. 4Refresh

    Reload the status after allowing a run to complete. Repeated button clicks do not establish state freshness.

  5. 5Sublot review

    A split review makes a fresh parent read. If that read fails, stop; the mirror quantity alone is not enough to authorize the split.

What success looks like

You know the age and status of the specific source record and can explain whether action is safe to continue.

If something goes wrong

Connected but stale

A valid token does not guarantee a successful latest report. Review the run error.

One report is fresh and another is old

Check each source independently. Avoid presenting one timestamp as freshness for all inventory and events.

A lot disappeared

Use missing-record guidance before assuming stock was sold, moved or deleted.

Still need help?

Send the workspace, facility, safe error and approximate time. Keep credentials and private activation links out of the message.

Contact supportSearch another guide