The most common onOffice sync problems, each with cause and fix. If none of these helps, contact support with the name of the affected object or contact.
Only about 100 objects are imported
- Restart the sync once ("Sync now").
- In onOffice, disable "only published objects" for the API user.
- Check that the API user may read objects (all).
All objects show "active"
- Open and save the field mapping once (releases skipped fields such as Status2).
- Click "Sync now"; already imported objects are corrected.
- For finer stages, map your own status value list (see the status guide).
"onOffice rejected the credentials"
- Check token and secret. onOffice shows the secret only once; regenerate if in doubt.
- Check whether the API user is active in onOffice.
- Store new credentials via "Replace" and click "Connect & test".
No or too few objects visible
- Disable "only published objects" for the API user.
- Check object rights (all).
- Check the status filter in the object gallery: sold and archived objects may be hidden.
A mapped field stays empty
- Save the field mapping once more (releases skipped fields).
- Check the exact field name (case-sensitive, as in onOffice).
- Check whether the API user may read the field.
The sync appears stuck
- Reload the page and check the run status.
- If needed, "Cancel" and then "Sync now" again.
Objects show no photos
- Wait a few minutes and reload the object gallery.
- Check that the API user may read objects (all) (photos depend on the object read right).
- Objects with no photo in onOffice keep the placeholder. A repeated sync fetches missing photos.
"Secure storage not configured"
The environment has no encryption key for credentials yet. In that case contact support; without this key credentials cannot be stored.