Troubleshooting
This page is a catalog of specific errors and messages you might see in MaxTrax, each with its own stable link so you (or someone helping you) can jump straight to what it means. If you land here from a link elsewhere in the app, you’re in the right place — the section below matching that link explains what happened and what to do.
Anchor stability contract
Section titled “Anchor stability contract”Every heading below is a stable link — once published, its anchor doesn’t change, even if the wording above it improves. Where a message comes from an internal reason code, that code is quoted so the two can always be matched up.
| Reason code (internal) | Section |
|---|---|
validation |
Validation failed |
domainRule |
Not allowed by a rule |
notFound |
Related record not found |
databaseRule |
Rejected by a database rule |
deleteUnsupported |
Deleting offline isn’t supported |
stateConflict |
Sync conflict |
descriptiveEditNotSupported |
Descriptive edit not supported (film interval) |
duplicateMutationForEntity |
Duplicate edit in one batch (film interval) |
facility_stencil_collision |
Facility stencil collision |
facility_procedure_code_collision |
Facility procedure code collision |
Sync errors
Section titled “Sync errors”These show up in the Needs attention list or the conflict dialog described in Working offline.
Validation failed
Section titled “Validation failed”The server rejected an offline change because it failed a data-validation rule (a required field, an out-of-range value, and so on). Open the item and select Review to see the underlying detail; fix the record and it will sync cleanly next time.
Not allowed by a rule
Section titled “Not allowed by a rule”The change was valid on its own, but broke a domain rule about what’s allowed in the current state (for example, a status change that isn’t legal from where the record stands). Review the record’s current state before retrying.
Related record not found
Section titled “Related record not found”The change referenced a record MaxTrax couldn’t find — either it was deleted, or it belongs to a project you don’t have access to. If you believe it should exist, check with your admin.
Rejected by a database rule
Section titled “Rejected by a database rule”The change conflicted with a rule enforced at the database level (for example, a uniqueness constraint). This is uncommon; if it recurs, contact support with the reference details from the Review view.
Deleting offline isn’t supported
Section titled “Deleting offline isn’t supported”Weld, inspection, and film-interval deletions aren’t supported while offline. Reconnect and delete the record online instead.
Sync conflict
Section titled “Sync conflict”An offline change conflicted with what happened to the same record on the server in the meantime. See Working offline for how to resolve it — you’ll always be offered Keep server, and Re-apply mine when your change is still valid to apply.
Descriptive edit not supported (film interval)
Section titled “Descriptive edit not supported (film interval)”An offline edit to a film interval’s descriptive fields (comments, begin/end position) isn’t supported — only its status can be changed offline. Make descriptive edits while online.
Duplicate edit in one batch (film interval)
Section titled “Duplicate edit in one batch (film interval)”Two edits to the same film interval were queued in the same offline batch. Make one change at a time to a given film interval before going offline again, or make the follow-up edit after the first has synced.
Import rejections
Section titled “Import rejections”These appear in the validation report described in Import weld data from Excel.
Wrong file type or size
Section titled “Wrong file type or size”MaxTrax only accepts .xlsx workbooks (not .xls, .xlsm, or password-protected files), up to
25 MB, and the file can’t be empty. Re-export or re-save your workbook in the required format
if you hit this.
Upload didn’t complete
Section titled “Upload didn’t complete”The upload can fail at a few points — starting the import, uploading to storage, or confirming it — usually from a connection hiccup or an expired upload link. Try again; nothing is queued until the upload fully confirms, so a retry is always safe.
Workbook couldn’t be read
Section titled “Workbook couldn’t be read”The whole run can fail before any rows import if the workbook itself isn’t readable — for example, a required worksheet is missing, the file isn’t a genuine .xlsx package, or it’s structured in a way MaxTrax can’t safely process. The run’s error names the specific problem; you’ll need to fix the workbook itself and start a new import.
A row was rejected
Section titled “A row was rejected”Most rejections are per-row: a blank required field, a value MaxTrax doesn’t recognize (like an unknown facility code, welder stencil, or inspection type), or a reference to an ISO or weld that isn’t in the workbook. The validation report names the sheet, row, field, and reason for each — use the Fix link where available to jump straight to the record.
Facility stencil collision
Section titled “Facility stencil collision”If your project is split into facilities, a welder stencil only has to be unique within each facility — the same stencil can be reused in a different facility without clashing. This rejection means the stencil you’re adding already exists in this facility, so MaxTrax can’t tell the two welders apart. Pick a stencil that’s unused in this facility, or confirm you’re working in the right facility, then retry.
Facility procedure code collision
Section titled “Facility procedure code collision”The same rule applies to welding-procedure (WPS) codes when a project uses facilities: a code only has to be unique within a facility. This rejection means the procedure code you’re adding already exists in this facility. Use a code that’s unused in this facility, or confirm the facility, then retry.
Sign-in & access
Section titled “Sign-in & access”Access required
Section titled “Access required”If a page needs a role you don’t have, MaxTrax shows Access required and names what’s needed (for example, “You need a Corporate Administrator role or higher…”). Ask your admin to grant it if you believe you should have access.
No projects assigned
Section titled “No projects assigned”If your account isn’t assigned to any active project, MaxTrax shows No projects assigned and asks you to contact an administrator to be added to one — without a project, there’s nothing to show.
Signed out unexpectedly
Section titled “Signed out unexpectedly”Sign-ins don’t last forever. Most of the time you’ll never notice: if yours is close to lapsing while MaxTrax is open, the app renews it in the background and you carry on working.
If it can’t be renewed — usually because you’ve been away long enough that the sign-in has fully lapsed — MaxTrax replaces the screen with Your session has expired and a Sign in again button. Nothing you had already saved is lost, including work still queued to sync from that device. Sign in again and carry on; if this happens often, let your admin know.
Performance
Section titled “Performance”Slow to load after being idle (cold start)
Section titled “Slow to load after being idle (cold start)”If MaxTrax seems stuck loading for a few seconds — most often first thing in the morning or after a period of no use — a note explains the server may be waking up after being idle. This resolves on its own within a few seconds and doesn’t need any action from you.
Related
Section titled “Related”- Working offline — the sync indicator, Needs attention list, and conflict dialog where sync errors surface.
- Import weld data from Excel — the import flow behind the validation report and its rejections.
- Reference — the exact rules MaxTrax enforces: state machines, roles, the import spec, and the report catalog.