Weld status lifecycle
Every weld has a status that records where it is in its lifecycle. MaxTrax permits only the transitions listed on this page; any other move — including a weld transitioning to the status it already holds — is rejected. The same rules apply everywhere a status changes: in the app online, when offline changes sync, and during Excel import.
The tables below are the authoritative reference behind the diagram.
Weld statuses and their transitions
Section titled “Weld statuses and their transitions”| Status | Meaning | Legal transitions to |
|---|---|---|
Pending |
A newly created weld, awaiting inspection or disposition. Every weld starts here. | Accepted, Rejected, or Voided |
Accepted |
The weld passed inspection, or an editor accepted it. | None (terminal) |
Rejected |
The weld didn’t pass — an inspection failed, or an editor rejected it. It is repaired by creating a linked repair weld. | Repair |
Voided |
The weld was cancelled or withdrawn from the workflow. | None (terminal) |
Repair |
The original rejected weld after a repair was requested — it has been superseded by a new repair weld. | None (terminal) |
Persisting |
A transitional state used only while Excel import loads rows, before they enter the live workflow. You never set it in the app. | Pending |
Terminal statuses — Accepted, Voided, and Repair — have no outgoing transitions. A
weld in one of them is final and can’t change again. Rejected is not terminal: its one legal
move is to Repair. Persisting is the import-only entry point into the lifecycle.
How each transition happens
Section titled “How each transition happens”| Transition | How it happens |
|---|---|
Pending → Accepted |
Recording inspection results — when every inspection on the weld has passed — drives it, or an editor sets it directly with the weld’s Change Status → Accept action. |
Pending → Rejected |
Recording an inspection as Failed drives it, or an editor sets it directly with Change Status → Reject. |
Pending → Voided |
An editor sets it directly with Change Status → Void. It is not inspection-driven. |
Rejected → Repair |
Requesting a repair from the weld’s drawer, which creates a new linked repair weld and retires the original. This is the only way a weld reaches Repair — you cannot set it with Change Status. |
Persisting → Pending |
Written only by the Excel import pipeline. No in-app action produces it. |
A few points auditors ask about:
- Change Status is available only while a weld is
Pending. Once a weld isAccepted,Rejected,Voided, orRepair, an editor can’t reclassify it. - Recording inspection results can drive a weld to
AcceptedorRejected, but never toVoidedorRepair. Repairis never an in-place status change. It always creates a new, linked weld — see Repair a weld.
Where these rules apply
Section titled “Where these rules apply”This is a single rule set. Whether a status change comes from the online app, from an offline change that syncs later, or from the Excel import pipeline, the transitions above are enforced identically — so a weld can never end up in a state these rules don’t allow.
Related
Section titled “Related”- Repair a weld — the
Rejected→Repairworkflow. - Record an inspection result — how inspections drive
AcceptedandRejected. - Inspection states — the separate lifecycle of an inspection result.
- Import weld data from Excel — where the import-only
Persistingstate comes from.