Live updates
When two people have the same Board open, each sees the other’s changes without reloading. Tasks lists, the Table view, the Hub and My Tasks follow along too.
What updates live
Section titled “What updates live”| Screen | How often | What changes |
|---|---|---|
| Board | Every 15 seconds | Moved, renamed, reassigned, new and deleted cards. Column counts follow. |
| Project Tasks tab | Every 15 seconds | Changed, new and deleted tasks. |
| Table view (task list block) | Every 15 seconds | Changed rows; new rows that match the filters in force. |
| Hub and My Tasks | Every 60 seconds | Changes to tasks assigned to you, and tasks newly assigned to you. |
A changed card or row shows a soft outline and a short “Updated by
Your own changes are not repeated back to you. A change made by an automation rule shows as “Updated by Automation (rule:
When the tab is in the background
Section titled “When the tab is in the background”Pages only ask for changes while their browser tab is in view. Switch to another tab and the page stops asking; come back and it catches up at once. If the connection drops, the page waits longer between tries (up to five minutes) instead of showing errors, and catches up when the connection is back.
A card you are dragging is never moved or redrawn under you. Changes wait until you drop it.
When two people change the same task
Section titled “When two people change the same task”If someone else saved a task after you opened it, saving yours shows “
- Keep mine saves your change over theirs.
- Reload shows their version and drops your change.
The same choice appears when you drag a card that someone changed a moment ago. The card stays where it was until you choose.
Clients
Section titled “Clients”Clients see live changes on the tasks they can see, on the project Tasks tab. They never receive anything about an Internal task (created, changed, moved or deleted) or a Team only comment, and they do not see who made a change. When a task they can see is marked Internal or deleted, it disappears from their list.
People removed from a project stop receiving changes straight away; a reload shows “Project not found”.
Turn live updates on or off
Section titled “Turn live updates on or off”Live updates are on by default.
- Go to Kanbanomy > Settings > General.
- Under Live updates, tick or clear Show changes from other people as they happen.
- Select Save Changes.
With the box cleared, no page asks for changes; everything else works as before and a reload shows the latest.
Live updates read the project activity log. With the Activity Log feature turned off (Kanbanomy > Settings > Features), live updates are off too, and the box says so.
Load on your server
Section titled “Load on your server”Each open page asks one small question: “what changed since the last time?”. The answer comes from one indexed query on the activity log, at most 100 changes at a time, and is never cached.
Measured on a test site with 10,000 users, 2,000 projects, 100,000 tasks and 200,000 activity entries (WooCommerce, LearnDash and BuddyPress active, one 10-core container):
| Measure | Result |
|---|---|
| Database work per poll (the change query itself) | 0.5 ms median, 1.9 ms at the 95th percentile, at most 8 queries |
| One poll, whole request | 0.12 s median, 0.16 s at the 95th percentile |
| 100 polls fired at the same instant, whole request | 2.2 s median, 3.3 s at the 95th percentile |
| The same 100 at once on the lightest existing request (the bell’s unread count), for comparison | 1.9 s median, 3.3 s at the 95th percentile |
With 100 requests arriving together the time goes to loading WordPress and its plugins once per request, not to live updates: the poll costs the same as the bell’s unread count. In normal use 100 open boards spread their polls across 15 seconds, about 7 requests a second. A page whose tab is in the background sends none.
For developers
Section titled “For developers”- REST:
GET /wp-json/kanbanomy/v1/projects/{id}/changes?since=<cursor>andGET /wp-json/kanbanomy/v1/me/changes?since=<cursor>. The answer is{ cursor, more, items }; each item is{ task_id, action, by_id, rule, subtask, by }, or{ task_id, gone: true }. A cursor of 0 returns only the current cursor. - Filter
kanbanomy_live_interval( $seconds, $where )changes how often pages ask ($whereisboardorhub; minimum 5 seconds). - Saves that send
expected_updated_at(task panel, Board move) get a 409task_changedwithdata.taskanddata.changed_bywhen someone else saved first.

