Sync and account problems

My document list is temporarily unavailable

If the server is busy or your connection is interrupted, Tylor may be unable to load the dashboard. This does not mean your documents were deleted. A failed request shows a recovery message instead of “Create your first document.”

Check your connection, then choose Try again. You do not need to reload the page. While retrying, the button reads Trying again…. A stalled request stops waiting after 20 seconds. The dashboard also checks again when you reconnect, return to the tab, and periodically while it is visible.

If the list loaded earlier in this session, its documents and folders remain visible with Showing the last successfully loaded list. That list may not reflect recent changes on other devices. The message disappears after a successful refresh. A package-library failure has its own message and retry action.

Changes stay queued

Keep the original browser profile open, reconnect, and inspect the sync error. Use the available retry control after resolving the cause. A server outage, expired sign-in, permissions change, or storage limit can prevent an upload.

Preserve an editable ZIP if possible before trying recovery. Clearing site data can remove unsynced changes and local-only projects.

Sync paused after repeatedly adding and removing text

An older version could pause sync with suggestion not found when you added and removed the same text while suggesting changes. It tried to delete a draft that had never reached the server, blocking later changes behind it.

Use Download pending changes to keep a recovery copy, then reload Tylor in the same browser profile with a connection. The updated app removes these draft-only blockers during sync and keeps pending document saves. Wait for the queued count to disappear before switching devices. If sync remains paused, inspect the error and use Retry; errors for saved suggestions, permissions, or other operations still need attention.

The downloaded JSON is a recovery record, not an importable project ZIP. Keep it until you have checked that your latest text reached the server. Do not clear site data to unblock sync.

Another device has an older version

Return to the device where you edited and check that it has finished syncing. Then reopen or refresh the document on the other device as prompted. A locally saved edit is not necessarily on the server yet.

I cannot edit a shared document

Check whether you are a viewer. You may also see an editing-presence lock, a collaboration mode-change prompt, or a notice that the project changed elsewhere. Follow the specific message before continuing.

Ask the owner to check both direct project permissions and inherited folder access.

I cannot sign in to my usual account

Use the original sign-in method. If you forgot an email password, choose Continue with email → Forgot password? on the sign-in screen and follow the emailed reset link. To add a password, Google, or GitHub to the same account, sign in first and open Account → Sign-in methods. A new email account receives a verification email; use Resend verification email in Sign-in methods if it does not arrive. Sign out and sign in again after verifying before accepting an invitation.

Separate accounts are not automatically merged. If an email is already associated with another sign-in method, follow the account recovery message rather than creating another workspace.

Account access can also depend on an invitation or administrator approval. Follow the access screen or contact the instance administrator.

A tool is missing

Sharing, review, AI, Git, and other server-backed tools are unavailable in local mode. Account permissions and instance configuration can further restrict them. Check the feature’s requirements in this guide before assuming the interface is broken.