---
title: "How to manually re-process failed changes from FieldBuddy Swift"
canonical: "https://help.fieldbuddy.com/space/FBDOCS/5674205185/How%20to%20manually%20re-process%20failed%20changes%20from%20FieldBuddy%20Swift"
format: markdown
---
On this page, there is a short guide that you could use to speed up recovery of failed changes from FieldBuddy Swift

> Macro (toc)

> ⚠️ Please read the entire guide before doing any changes or trying this out.

## Prerequisites and Warnings

- It is necessary to have a System Administrator profile in order to perform the changes with FieldBuddy license assigned
- It is necessary to have a configuration assigned for your user and it should be active (so in status Current) You can use the Swift API tool and make a request with type `USER_CONFIG` to have new config the config to be assigned.

![image-20260701-150218.png](media://a3a6c58b-6641-4e4f-8265-f8f74db14ddb)

- Changes that are done will be done on behalf of your current user (and not based on original one)
- It might be necessary to have a config assigned that does have **applyOnlyUserChanges** set as false (more about it here - [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/3107914303](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/3107914303) ) in order to process changes on work order when owner is different then current user.
- It might has sense to also keep briefcase for such configuration for data recovery very small (for example, only current user)

## Preparations Steps

1. Open a Configuration Panel
2. Go to Setup FieldBuddy Swift
3. In top right corner, click on Extra Options. Few more tabs will appear. Open tab Swift API test tool
  
4. This is the tool that allows to send swift-like payloads to it will be processed by a back-end  
First step is - make inital sync. That could be done via clicking on Sample Request and then Send Request
  
5. After that, it is possbile to copy the “failed changes” into API request and process them via Send Request button. It makes sense to to them group them that changes from same mobile sync log are in same request

## Processing of failed changes

1. Open tab Sync Overview and  find a failed sync log, changes from which you want to re-apply
  
2. In this case, there is a failed update to IP due to read-only field. So to re-try the change, open the tab  Request at the right side, and copy “Changes” array with square brackets
  For example,
3. After that go back to the Swift API Sync Test Tool, and unwrap at the bottom the Changes Only section
  
4. After that paste the array and click on “Arrow up” button - Changes will be applied to the request
  
5. ⚠️ Increase Sync ID (so if it was 0 -> make it 1, for example) THIS IS IMPORTANT. Without it – changes will not be processed
6. Click Send Request - The right part of the page should be updated with the Status - success: and updated sync id
  
7. Thats it. Repeat the sequence from 1 to 7 for all the failing changes

## Other important notes and considerations

1. Sometime changes have dependencies on another objects (for example, creation of new checklist questions or timesheet line items). It is possible to determine this by following line  
`"FIELDBUDDY__Work_Order_Line_Item__c" : "__FB__TEMPLATE_TYPE_FIELDBUDDY__Work_Order_Line_Item__c_2193555a9332c1e75795484a1cde532a"`

To approach this problem, it is necessary to find original mobile sync log, and pick the proper parent record id (in case above – WOLI id) that was created as part of the sync process.`"FIELDBUDDY__Work_Order_Line_Item__c" : "a17R300000R2qjOIAR"`

2. It makes sense to process failed changes that create WOLI + WOLID in one call to do not do a lot of manual work by replacing ids. (So for example, all of the reference of the same Work Order Line Item Id should be in one chunk, like `__FB__TEMPLATE_TYPE_FIELDBUDDY__Work_Order_Line_Item__c_2193555a9332c1e75795484a1cde532a`)

> ℹ️ Click [here](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/4940955674) for a refresher on how to assign a configuration file to a user.

## \uD83D\uDCCB Related articles

- [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/3094808809](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/3094808809)
- [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5365268532](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5365268532)