> ## Documentation Index
> Fetch the complete documentation index at: https://docs.farmtrace.co.za/llms.txt
> Use this file to discover all available pages before exploring further.

# Sync and connectivity

> Know what Dsync can do locally and what to check when synchronization needs attention.

Dsync separates field work from the moment a server confirms it. A record can be captured locally first and synchronized later, but a local success is not the same as a server-side success.

## What to expect

| Situation                      | Expected behavior                                                                  |
| ------------------------------ | ---------------------------------------------------------------------------------- |
| Stable connection              | Dsync can retrieve configured data and exchange completed records.                 |
| Intermittent connection        | Continue with data already available locally, then sync when connectivity returns. |
| Expired or invalid session     | Re-authentication is required before protected data can be exchanged.              |
| Missing table or record access | The server can reject the request even when the device is online.                  |
| Upload result is unclear       | Wait for the app's final state before submitting the same work again.              |

<Info>
  Server permissions remain authoritative. A local copy can help you keep working, but it does not grant access to a database, table, or record.
</Info>

## A safe sync check

<Steps>
  <Step title="Check the account">
    Confirm that the user is signed in and that the session has not expired.
  </Step>

  <Step title="Check the network">
    Move to a reliable connection and confirm that other network activity works on the device.
  </Step>

  <Step title="Check the scope">
    Confirm with an administrator that the account can access the database, table, and fields involved in the operation.
  </Step>

  <Step title="Check the result">
    Use the visible success, pending, or error state. If a request could have reached the server, do not blindly create a duplicate while the result is unknown.
  </Step>
</Steps>

## When records appear stale

1. Check the last successful sync or the message shown by Dsync.
2. Confirm that the record is not still pending locally.
3. Verify that the current account can access the source table.
4. Reopen the record after a successful sync.
5. If the value still differs, capture the record identifier and contact your administrator.

## When a sync fails

Start with the exact error. A permission error needs an administrator; a session error needs sign-in; a network error needs connectivity; and a malformed or conflicting record may need its values corrected before retrying.

<Tip>
  Include the account, record identifier, operation, time, connection state, and exact error text when contacting [support@farmtrace.co.za](mailto:support@farmtrace.co.za).
</Tip>