Skip to content
Source
Sign inSign up

Change issues offline

Stay on top of work

Change issues while offline

Your connection drops while you work on issues, and you do not want to lose a comment. Source saves supported changes on this device, and sends them when the connection returns.

3 min read

1. Open your pages while you are online

Sign in, and open the issue lists, issues or pull requests that you need. Your browser saves the collaboration pages that you visit, and their loaded data.

Tip

To create an issue offline, open the new issue form before you go offline.

2. Keep working in the same tab

On items created in Source, these changes show at once:

  • comments,
  • the open or closed state,
  • labels and assignees,
  • pins and conversation locks.

A new issue shows in the list with Waiting to sync, until the server gives it its number.

A Source pull request conversation with its comment, labels and conversation tab.

Note

Changes to items synced from GitHub need a connection.

A screen reader announces a pin or a lock as done (Issue pinned., Conversation locked.) only after the server accepts it. Offline, it announces Saved on this device. It syncs when you are online.

3. Read the notice

The notice below the header shows what waits. For example, 2 changes waiting to sync. Saved on this device. means that the changes are in browser storage. You can reload the saved page and keep the changes.

  • Click Show changes to see each change, and why it waits.
  • If another tab owns offline sync, Source asks you to use that tab, or to reconnect before you save.

What the notice says lists each notice.

4. Reconnect

Source sends the changes in order, and checks your current permissions.

  • Its SSE subscription streams the accepted rows into the page.
  • Each change on the page settles when that server cursor arrives.
  • A repeated delivery uses the same operation id, so a retried comment is not posted twice.

5. Check for a refused change

If the server refuses a change, the notice says Not saved:, then the change and the reason. Source rolls back that change on the page. See Fix a change that was not saved.

Done

Your changes reached the server, and the notice is gone. When something does not sync, the notice says what, why and what to do.

What the notice says, and what to do

The notice below the header shows only when something is not normal.

The notice saysWhat it meansWhat to do
3 changes waiting to sync.Source sends the changes now.Nothing. Click Show changes to see why each one waits.
3 changes waiting to sync. Saved on this device.You are offline. The changes are in browser storage.Reconnect. Source sends them.
Offline. Showing saved data.The browser has no connection.Reconnect.
Live updates stopped. The page shows the data from a time . Reload to see new changes.You are online, but the live updates from the server failed. Your changes still go out.Click Reload data.
Not saved:, the change, and the reasonThe server refused the change.See Fix a change that was not saved.
You were signed out. Sign in again to see your data.The server ended your session. Source removed your data from this device.Click Sign in.

Under Show changes, each change says why it waits:

  • Waits for a connection.
  • Sending now.
  • Sends again after an error., then the error.

When a change fails for another reason, the notice shows the error. Click Reload data to load the page data again.