Read the current state
Offline or pending indicators mean that some work has not yet been confirmed by the server. A change can be visible locally before it reaches your other devices.
Supported native task writes are stored locally and retried on reconnect. Previously cached content can be available offline, but a new device cannot retrieve uncached content without a connection.
Reconnect and verify
- Restore a working connection and open the app.
- Allow pending synchronization to run.
- Read any retry, conflict, or permission message.
- Check the result before expecting it on another device.
Review a blocked change on the web
Using the server version discards the affected local edit and does not change the server. That choice cannot be undone. Copy any text you need before discarding it.
Some structural changes must use the server version before you reapply the move to the latest task layout. Editing may also be unavailable because the task was deleted or your access changed. Reconnecting alone cannot resolve a change that needs this decision.
- Choose the changes need attention · Review control.
- Choose Compare versions and read On this device and On server for the affected fields.
- Choose Keep my change and retry if it is available and your edit is still intended. Choose Use server version to cancel the local edit, or Cancel local change when the task is unavailable.
- Read the confirmation, then choose Confirm choice. Use Refresh comparison if you need the latest server state, or Decide later to leave the decision pending.
Read native sync messages
Syncing changes means uploads are in progress. Offline · changes saved means work is retained on this device. Changes need attention requires review. Up to date means the sync status currently reports no pending writes.
Native task review also compares saved changes with the server and confirms your choice. A saved retry can still be waiting for a connection. Sharing permissions, membership and external account connections need a live authenticated connection.
Native sign-out is blocked while offline mutations remain. Restore connectivity and resolve any review items instead of uninstalling to bypass that protection.
Keep local-only work safe
Do not clear browser/app data, uninstall, or force a sign-out while important changes are still pending. Those actions can remove the local copy before it has synchronized. Use support if a queue remains stuck.