---
title: "More about Mobile Sync Logs"
canonical: "https://help.fieldbuddy.com/space/FBDOCS/6310363147/More%20about%20Mobile%20Sync%20Logs"
format: markdown
---
Every single record of Mobile Sync log represent a sync operation of FieldBuddy Swift.

It has attachments with request and response stored as well as some helper information, as well as status, amount of changes and mobile app version

> ⚠️ Some of fields and custom UI component is only available since package version 1.146.0

![image-20250820-154209.png](media://8b182887-97f5-44e4-9b8c-f5d4f7074d8d)

> ℹ️ It makes sense to use Sync Overview [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5539692561](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5539692561) to navigate there since it gives a good perspective of changes


There are following statuses that Mobile Sync Log can have:

- Draft - mean that processing of changes is in progress and Swift is still syncing
- Processed - mean that sync is completed, and all changes are processed
- Processed Zero - mean that sync is completed, this log is an indicator that Swift had a hard sync or just logged in
- Duplicate - occurs in case if Swift tries to apply same payload 2nd time, changes from those are not processed (since they must have been processed in sync before)
- Failed - Failed means that there is a sync issue or more changes are not processed due to various reasons (like no access, BE validations etc)

There are couple of more statuses that represent async processing of changes to make sure that all the changes from Swift are applied in Service Center 

- Pending Async
- Processed Async
- Failed Async

Mechanism works as follows - in case if Swift can not perform sync of changes due to plethora of ones, it will try to process them in chunks. Chunk size or other options could be configured here - [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5539692561/FieldBuddy+Swift+Settings+in+Configuration+Panel#Extra-Settings](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5539692561/FieldBuddy+Swift+Settings+in+Configuration+Panel#Extra-Settings) 

In that case, mobile sync log will be created in status Pending Async. It means that there is an async job (or few) that is processing the changes. As soon as all the jobs are completed, status will be updated to Processed Async, and Swift will receive sync 0 to get all the latest set of data from Service Center

Failed async mean that async processing of changes did not go well (because of the limits for one more more chunks) or there are 1 or more failed changes.  
In case of the first scenario, there are not logs created for failed chunks, (due to salesforce’s limits issue — nothing is saved) so it is safe to consider that no changes were processed at all! In that case, you will be able to observe failed logs in Setup → Apex Jobs  
In case of 2nd scenario, there will be individual attachments with the chunk number and status of each change (if it is processed or unprocessed)

> ℹ️ In case if there are Failed changes - then check the following guide how to re-process those - [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5674205185](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5674205185)