From 41b8dfa08d3d26b33b13f6d0671dd80264448e73 Mon Sep 17 00:00:00 2001 From: zubaira Date: Thu, 8 Jan 2026 12:22:53 +0100 Subject: [PATCH 1/2] docs: single event and tracker data synchronization job --- src/developer/web-api/scheduling.md | 23 ++++++++++++++++++++++- src/user/scheduling.md | 6 ------ 2 files changed, 22 insertions(+), 7 deletions(-) diff --git a/src/developer/web-api/scheduling.md b/src/developer/web-api/scheduling.md index 208bb9ae0..37e2afb42 100644 --- a/src/developer/web-api/scheduling.md +++ b/src/developer/web-api/scheduling.md @@ -78,7 +78,8 @@ Table: `DATA_SYNC` job parameters | Name | Type | Default | Description | |---------------|---------------|---------|--------------------------------------------------| -| `pageSize` | int | `10000` | number of data values processed as a unit | +| `pageSize` | int | `10000` | number of aggregate data values processed as a unit | +| `pageSize` | int | `60` | number of events or tracked entities processed as a unit | Table: `META_DATA_SYNC` job parameters @@ -179,6 +180,26 @@ An example of a job with scheduling type `FIXED_DELAY` and 120 seconds delay: } ``` +An example of scheduling a job to synchronize single event data + +```json +{ + "name": "Single event data synchronization", + "jobType": "SINGLE_EVENT_DATA_SYNC", + "cronExpression": "0 * * ? * *" +} +``` + +An example of scheduling a job to synchronize tracked entity data + +```json +{ + "name": "Tracked entity data synchronization", + "jobType": "TRACKED_ENTITY_DATA_SYNC", + "cronExpression": "0 * * ? * *" +} +``` + ### Get Job Configurations List all job configurations: diff --git a/src/user/scheduling.md b/src/user/scheduling.md index c6118571c..204f0fb95 100644 --- a/src/user/scheduling.md +++ b/src/user/scheduling.md @@ -275,12 +275,6 @@ Some aspects of the data synchronization feature to be aware of: synchronization time is tracked individually for each item as previously mentioned. -- The attributes of TrackedEntityInstances (TrackedEntityAttribute) and the data - elements of ProgramStages (ProgramStageDataElement) which have an option "Skip - synchronization" turned on will not be synchronized. This feature allows you - to decide to not synchronize some sensitive or not relevant data and to keep - them only locally. - - The authority `Ignore validation of required fields in Tracker and Event Capture` (`F_IGNORE_TRACKER_REQUIRED_VALUE_VALIDATION`) should be used when there From 674e11a74af78c6ce04417ba2ad2288449afc8da Mon Sep 17 00:00:00 2001 From: zubaira Date: Thu, 8 Jan 2026 12:24:45 +0100 Subject: [PATCH 2/2] minor --- src/user/scheduling.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/user/scheduling.md b/src/user/scheduling.md index 204f0fb95..83b6ed8cc 100644 --- a/src/user/scheduling.md +++ b/src/user/scheduling.md @@ -275,6 +275,11 @@ Some aspects of the data synchronization feature to be aware of: synchronization time is tracked individually for each item as previously mentioned. +- The data elements of ProgramStages (ProgramStageDataElement) which have an option "Skip + synchronization" turned on will not be synchronized. This feature allows you + to decide to not synchronize some sensitive or not relevant data and to keep + them only locally. + - The authority `Ignore validation of required fields in Tracker and Event Capture` (`F_IGNORE_TRACKER_REQUIRED_VALUE_VALIDATION`) should be used when there