Sync health, logs and recovery

Every connection tells you how it is doing — at the connection level, per board and per item. This article covers where to look, what the states mean, and how to get sync moving again when it stalls.

Connection health at a glance

Each connection has a manage page in your workspace settings' integrations area, with three tabs: Boards, Sync log and Settings. The page shows the connection's health, the last sync time and the most recent error message, and updates live as things change.

• Health states include Healthy, Degraded, Needs attention and Idle.
• The connections list in your workspace settings labels the same conditions slightly differently: a connection shown there as Broken appears on the manage page as Needs attention, and one shown as Disabled appears as Idle.
• Jira connections have a Test connection button that probes the site on demand and updates the health state from the result.
• The Boards tab lists every mirrored board with its freshness, its own Sync now, and management actions.

Reading the sync log

The Sync log tab is a read-only, newest-first record of the connection's last 100 sync operations. Each entry shows when it happened, the direction (↓ from your tool, ↑ to your tool), the item involved, the action taken, and a state badge — queued, syncing, retrying, succeeded or failed. Failed entries expand to show the error and payload details, and the list refreshes live as new events arrive.

Per-item sync status

• A linked item's detail panel shows a compact chip: a green dot with 'synced' and a relative time when healthy, or amber with 'sync paused'. It expands into the item's sync controls.
• Connected-board cards carry a footer badge with states such as synced … ago, syncing…, conflict, failed — retry and pending.

Pausing and resuming sync

• Per connection: the Settings tab has a Polling toggle controlling background polling for that connection (you will see 'Polling enabled' or 'Polling disabled' confirmations). Manual Sync now always works regardless.
• Per board: Board settings → Integrations lists each provider with a sync toggle. As the tab explains, turning a provider off 'pauses syncing for all linked issues — the links stay, so turning it back on resumes where it left off.' State chips show Connected, Paused or Not connected.
• Per item: Jira-linked items offer Pause sync and Resume sync in the detail panel; resuming re-pulls the latest from Jira. Before using Remove link, note the inline advice: 'Pause sync instead — that keeps the link so you can resume anytime.' Per-item pause controls are currently available for Jira-linked items only.

When sync stalls

1. Check the connection's healthOpen the connection's manage page. A Degraded or Needs attention state, or a recent error message, usually names the cause. On Jira, use Test connection to re-probe; on other providers, run Sync now and check the sync log.
2. Check for pausesLook for a Paused chip in Board settings → Integrations, a 'sync paused' chip on the item itself, and the connection's Polling toggle.
3. Run Sync nowFrom the board or the connection's Boards tab. On a master board, use Sync all boards to pull every source at once.
4. Read the sync logFailed entries show the error and exactly which operation stopped.
5. Still stuck?Work through Sync not updating, or contact support.

Reconnecting after your credentials expire

When a connection's authorisation expires or is revoked, Laya marks the connection and stops syncing until you re-authorise. Your boards and their data are kept.

• Jira: an expired authorisation shows 'Jira authorization expired — reconnect required.' Reconnect from the connection page: Re-establish connection (or Refresh credentials) runs the connect flow again.
• Laya Board for Jira app connections: re-establish in one click — Laya pings the installed app and usually confirms within about 30 seconds; if not, open the Laya Board app in Jira and choose Reconnect.
• Azure DevOps: sign-in (OAuth) tokens refresh automatically in the background; if the connection degrades, Refresh credentials on the connection page re-runs the connect flow.
• monday.com: API tokens do not expire, but if you revoke the token in monday.com, requests fail until you reconnect with a fresh token.