Connection problems and offline behavior

Kanroo tells you when your browser has no network connection, when the Kanroo server cannot be reached, or when only live updates are unavailable. These states have different effects.

What can I do without a connection?

Content already loaded in the current tab can remain visible. You can read it and navigate within content that is already available. Kanroo may show a connection notice because this content can be out of date.

Kanroo does not provide a complete offline board. Server data is not cached for offline editing. While the connection is restricted, Kanroo prevents changes such as creating or editing tasks, submitting a public form, uploading a file, or signing in.

Local text that you have not submitted can remain in the open page. Keep the tab open until you decide whether to submit or discard it.

Are failed changes sent later?

No. Kanroo does not queue or automatically replay failed changes.

After the connection returns, submit the change again if you still want it. This rule prevents an old task change, form submission, upload, or sign-in code from being sent without your knowledge.

What do the connection messages mean?

No network connection means the browser reports that it is offline. Check Wi-Fi, Ethernet, airplane mode, a VPN, or another browser network setting.

Kanroo cannot be reached means the browser has a network connection, but a Kanroo request did not reach the server. The server may be restarting, the route may be interrupted, or a proxy may be unavailable.

Kanroo reported a server error means Kanroo answered, but it could not confirm your session. Wait a moment and try again. This is different from being signed out.

These messages do not mean that Kanroo deleted your data or ended your session.

Why do I see the Kanroo unavailable page?

Kanroo must confirm your session before it opens a protected page. If that check cannot finish, it opens Kanroo is unavailable instead of showing a sign-in form.

The page keeps your intended destination. Select Try again after the connection returns. If your session is still valid, Kanroo returns to that destination. If the server confirms that you are signed out, Kanroo opens sign-in and keeps the same destination for after sign-in.

If a protected page was already open when the connection failed, Kanroo normally keeps that page visible. It does not move a running page to the unavailable page.

The unavailable page requires a previously cached application shell. On a browser’s first visit, the browser can show its own network error if Kanroo is already unreachable.

How does recovery work?

The connection notice and the unavailable page provide Try again. Kanroo can also check once when the browser comes online or when you return to the tab. It does not continuously poll the server for general connection recovery.

Only a successful answer from Kanroo restores server actions. A browser reporting that it is online is not enough by itself.

Recovery removes the connection notice and restores affected reads and controls. It never submits a failed change automatically.

Closing the connection notice only hides the message. It does not restore the connection or enable changes.

What happens on public boards and forms?

Public boards, public forms, and submission receipts show their own load or submit error together with the connection notice. They can recover without personal sign-in.

If a public-form submission fails, review the entered values after the connection returns and submit the form again yourself. Kanroo does not create the request in the background.

What happens during sign-in?

Kanroo treats a failed session check differently from a confirmed signed-out session. A failed check opens the unavailable page. A confirmed signed-out session opens the normal sign-in page.

Failed email-code requests and verifications are not replayed. After recovery, request a new code when the page asks for one and submit it yourself.

SSO sign-in first checks whether the installation offers single sign-on (SSO). If that check fails, the page says SSO sign-in could not be loaded and offers Try again. It does not claim that SSO is unavailable. After recovery, the normal SSO sign-in form returns without discarding the selected organization or final destination.

SSO is not available appears only when the Kanroo installation successfully confirms that it does not offer this feature.

Why are live updates reconnecting while everything else works?

Realtime uses a separate connection for live board and task updates. If only this connection fails, Kanroo says Live updates are unavailable. Reconnecting… Normal reads and writes can continue.

Kanroo retries the Realtime connection while it is unavailable. These requests are expected and do not mean that changes are being repeated. When the stream returns, Kanroo says Live updates reconnected.

If the whole Kanroo server cannot be reached, the separate connection notice and write restriction apply instead.

What should I do?

1. Check whether the browser reports that it is offline.
2. Keep tabs with unsent text open.
3. Wait for the network or Kanroo server to return.
4. Select Try again once.
5. Review the page and submit any failed change again only if you still want it.
6. Contact your Kanroo administrator if the server remains unavailable.