You are here:
Troubleshooting Sync Errors
Here’s a list of troubleshooting steps you can use to resolve sync errors.
Required Editions
Available in: Lightning Experience Available in: Agentforce 1, Einstein 1, Enterprise, and Unlimited editions with Consumer Goods Cloud Retail Execution and Agentforce for Consumer Goods Cloud add-on licenses. |
| For Log Message | Action |
|---|---|
| Named query execution failed,Stage: Download descriptor, Error Originates From:CLIENT | Check if the Named Query is referring to valid objects and columns. |
| Named query execution failed,Stage: Download descriptor, Error Originates From:SERVER | Correct the Named Query. Ensure that for creating a custom field, __c is appended after the custom field name. |
| Named fetch tree: NFT_Listing_Classification evaluation failed. Stage: Evaluating a named fetch tree, Error Originates From: SERVER | In the Named Fetch Tree (NFT) page, check whether the contracts in mobile devices have the same NFT name as in the server. |
| The sync failed to complete, Stage:Executing sync, Error Originates From: SERVER | Check the related Tracked Objects in the Tracked Object page. If you’re using a custom field, ensure that the custom field name is appended with __c. |
| Failed to upload 1record(s), Stage:Uploading tracked objects, Error Originates From:SERVER | Check the user’s permission set to ensure that the user has access to the relevant Tracked Objects. |
| TQException: 9452 -ArgumentError:theFetchTreeName has to be a non-blank String. | |
| TQException: 9806 -File download skipped due to size is larger than MaxBinaryFileSize limit: 8388608 | Increase the Max File Size from the Mobile Settings page. |
Hjalp denne artikkelen med å løse problemet ditt?
La oss få vite det slik at vi kan forbedre!
