xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
Auto DMSConsumer Goods DMSSales Force Automation (SFA) FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Mobile Sync Failure — entity reference
REFERENCE · Last reviewed

Mobile Sync Failure — entity reference

A report that the xMatix mobile app files when a change queued on a device fails for good: the server refused it, it conflicted with a newer server version, or temporary errors used up all five attempts. The device sends the report through its own offline queue, so a failure that happens without coverage still arrives once the device reconnects. Each record carries what the device tried to write, the server's error, the device, user and app version, and a Resolution Status that administrators use to work the queue. Reports are evidence only: editing, resolving or deleting one never re-sends or discards the change still waiting on the device. In the standard setup the reports appear in the Field Sales app under Settings, Diagnostics, and nothing deletes them automatically.

Fields

FieldLabelTypeRequiredWhat it does
AppVersionApp VersionText, inactiveVersion of the mobile app that filed the report. Useful for spotting failures limited to devices that have not updated.
AttemptCountAttempt CountNumber, inactiveHow many times the device tried to send the change before giving up. A refusal on the first try shows 1; temporary errors that used up every attempt show 5.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DeviceIdDeviceText, inactiveIdentifier of the installation that filed the report. It stays the same for one installation of the app, so several reports with the same value point at one phone.
ErrorMessageError MessageLongMultiLineText, inactiveThe server's error as the device recorded it, as a title and message separated by a colon. Cut off after 4000 characters.
FailureReasonFailure ReasonPickList, inactiveRejected when the server refused the change (a validation, permission or not-found error) or when temporary errors such as time-outs, server errors or rate limits persisted through all five attempts. Conflict when the server reported that the record had changed or been removed since the device read it. The seeded Blocked value is never written by the device.
IdIdGuidYes
LastAttemptUtcLast Attempt (UTC)DateAndTime, inactiveWhen the final, failing attempt was made, in UTC.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYesShort headline the device writes: the internal name of the record type, the operation and the word failed, for example Order Create failed.
OccurredUtcOccurred (UTC)DateAndTime, inactiveWhen the change was first queued on the device, in UTC.
OperationOperationPickList, inactiveWhat the failed change was trying to do: Create, Update, Delete, Action (running an action, or a queued call to a dedicated endpoint) or UploadFile (a photo or attachment upload).
OwnerIdOwnerLookup → UserAccountYes
PayloadPayloadLongMultiLineText, inactiveThe data the device tried to send, as JSON text. Cut off after 4000 characters, so a long payload may be incomplete.
RecordTypeIdRecord TypeGuid, hidden
ResolutionNotesResolution NotesLongMultiLineText, inactiveShown on the standard record form, but the value has no storage on this record type: saving a value is refused because the field is inactive. Leave it empty.
ResolutionStatusResolution StatusPickList, inactiveTriage state for administrators: Open, In Progress, Resolved or Won't Fix. The device files every report as Open; nothing else changes it automatically. Changing it does not affect the change still waiting on the device.
ResolvedUtcResolved (UTC)DateAndTime, inactiveShown on the standard record form, but the value has no storage on this record type: saving a value is refused because the field is inactive. Leave it empty.
SourceEntityNameSource EntityText, inactiveInternal name of the record type the failed change was for, such as Order or VisitRouteStop.
SourceRecordIdSource Record IdText, inactiveIdentifier of the record the failed change targeted. For a create that never reached the server it is a temporary identifier generated on the device, which matches no server record.
SubscriptionKeySubscription KeyGuid, hiddenYes
UpdatedDateTimeUpdated OnDateAndTimeYes
UserNameUserText, inactiveDisplay name of the user signed in on the device. When the name has not loaded yet, for example during a background sync, the device writes the user's sign-in identifier instead. Created By always identifies the user whose session filed the report.

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
DeleteEntityDeleteDeleteDeleteEntity