Sync not updating

Symptoms

• A change made in your connected tool hasn't appeared in Laya.
• A change made in Laya hasn't appeared in the connected tool.
• A card's badge is stuck on "syncing…", "pending" or shows "failed — retry".
• An edit you made seems to have been overwritten.

First: know the expected speed

Not every direction is instant, and "slower than instant" is often working as designed. Edits made in Laya push to the connected tool immediately, as part of the edit itself. Inbound speed depends on the tool:

Likely causes

• Connection health is degraded, or the authorisation has expired.
• Sync is paused for the board (Board settings → Integrations shows a Paused chip) or, on Jira-linked issues, paused for the individual issue.
• The connection's Polling toggle is off.
• The connected account lost permissions on the provider side.
• A conflict: both sides changed the same item, and the newer edit won.
• The workspace is in a read-only state — inbound mirroring stops silently, with no error shown.
• The operation genuinely failed — the sync log has the error.

Fix it

1. Press Sync nowOn the affected board. On a master board, use the Sync all boards menu action to live-pull every connected source at once.
2. Check connection healthOpen the connection's Manage page (Settings → integrations). Look at the health card, Last sync and the last error message, and press Test connection where available.
3. Check pause statesBoard settings → Integrations lists each provider with a chip: Connected, Paused or Not connected. Turning a provider back on resumes where it left off — the links are kept. Also check the connection's Polling toggle, and on a Jira-linked issue, the Pause sync / Resume sync control on the issue panel.
4. Reauthorise if the connection expiredAn error such as "Jira authorization expired — reconnect required." means sync is stopped until you reconnect — use Refresh credentials or Re-establish connection on the Manage page, then follow the guide for your tool.
5. Check provider-side permissionsCan the connected account still open the project, board or repository in the tool itself? Laya can only sync what that account can reach.
6. Read the Sync log tabEach connection's Sync log lists recent operations with a direction arrow and a state (Queued, Syncing, Retrying, Synced, Failed). Expand a Failed row for the provider's error. There is no retry button on log rows in the current version — to push again, re-apply the edit in Laya; to pull again, press Sync now.
7. Understand conflicts before "fixing" themLaya resolves simultaneous edits with last-writer-wins: if both sides changed an item, the newer change is kept and the older one is skipped. On Jira boards a card can briefly show a "conflict" badge — Jira is treated as authoritative ("Jira changed while a Laya update was in flight."). Azure DevOps rejects stale writes outright and the next poll reconciles. In both cases, let the board refresh, then re-apply your edit if it's still wanted.

Verify the fix

• Make a small test edit in Laya and confirm it appears in the connected tool.
• Make a small test edit in the tool and confirm it reaches Laya — instantly, on the next poll, or after Sync now, per the table above.
• The card badge settles on "synced" with a recent time, and new Sync log rows end in the Synced state.

If you're still stuck

Email support@laya.net with: the tool and board involved, the direction that's failing (into Laya, out of Laya, or both), the connection's health word and last error, one failed Sync log row with its expanded error, and the timestamps of a test edit on each side.