Batching

Property and content events aren’t sent immediately. Changes of the same kind to the same target are collected for 60 seconds and sent as one event.

​

60-second batching

An event goes out 60 seconds after the first change. Later changes don’t extend the 60 seconds. timestamp is the time of the first change.

​

Events sent right away

These events aren’t collected. A check that runs every 2 seconds sends them.

• page.locked, page.unlocked
• data_source.content_updated
• comment.created, comment.updated, comment.deleted

​

Merged or skipped events

​

Edits right after creation

Properties changed within 60 seconds of creation are absorbed into page.created. No page.properties_updated is sent, and only authors merges. Values set during creation never arrive as page.properties_updated, for either subscription. Content changes aren’t absorbed and arrive as page.content_updated.

​

Reverted values

​

Delete and restore

​

Rows with subpages

Trashing, restoring, and moving send one event for the topmost target only. Deleting a row that has subpages sends just that row’s page.deleted. Deleting a subpage first and then the row sends both.

​

Changes before a subscription is on

Changes made before verification or before resuming aren’t sent. Later changes are sent, even if they fall inside a 60-second period that started earlier.

​

Arrival order

Each subscription sends up to 5 events at the same time, so arrival order can differ from change order. When many changes happen at once, events wait and go out in turn. Don’t rely on an event for state. Call the API with the IDs you received to read the current value.