monday.com connection issues

Symptoms

• Edits from Laya fail, and the connection's health is Degraded or Needs attention.
• Changes made in monday.com don't appear in Laya.
• Items sit in the wrong columns on the mirrored board.
• Subitems from monday.com are nowhere to be found.
• The assignee set on an item changed in a way you didn't expect.

Likely causes

• The personal API token was revoked or regenerated in monday.com. Tokens never expire on a schedule — they work until revoked, after which every request fails and the connection must be re-made.
• The board's status signal was auto-detected from the wrong column — a monday.com board's status can come from a Status column or from its groups.
• Subitems are not supported — they are not mirrored or imported, by design.
• People-column edits from Laya replace the whole assignee set.
• Fresh data hasn't been pulled — a mirrored board opens from Laya's synced copy, and background polling for monday.com is not always on.

Fix it

Reconnect after a revoked or regenerated token

1. Get a fresh tokenIn monday.com: Profile → Developers → My access tokens, then copy your personal API token.
2. Reconnect in LayaRun the connect flow again and paste the token under "Connect with an API token".
3. Confirm health recoversThe connection's Manage page should show Healthy and a fresh "Synced X ago".

Items land in the wrong columns

Laya auto-detects which column drives each signal — status, people and date — and, for boards without a Status column, falls back to the board's groups as lanes. If the guess is wrong, you can override it: open the mirrored board's column mapping and pick which column drives each signal. The mapping is saved per board.

Changes made in monday.com aren't arriving

1. Press Sync nowThis re-reads the board from monday.com and toasts "Synced N item(s)." — it's the dependable refresh path.
2. Check the Polling toggleThe connection's Settings tab has a Polling toggle. When polling isn't running, a mirrored board only refreshes on Sync now, at mirror time, or when someone edits through Laya.
3. Check the Sync log tabFailed rows expand to show the error monday.com returned.

Subitems and fields that don't sync

These are design limits in the current version, not faults:

• Subitems are not mirrored or imported, and subitem/progress columns are hidden on the item panel.
• For cards imported to a master board, only title, status and due date push back to monday.com — priority, story points, assignee and issue type do not push.
• Flowing the other way, imported cards continuously receive title and status only.
• Attachments are not synced or imported.

Verify the fix

• Sync now completes with "Synced N item(s)." and no failed rows appear in the Sync log.
• The connection's health card shows Healthy.
• A test change in monday.com appears in Laya after a Sync now.

If you're still stuck

Email support@laya.net with: the monday.com board name, whether the API token was recently regenerated (never include the token itself), which column drives status on that board (Status column or groups), and one failed Sync log row with its expanded error.