1e41f4b71Sopenharmony_ci# Distributed Scheduler Subsystem ChangeLog
2e41f4b71Sopenharmony_ci
3e41f4b71Sopenharmony_ci## cl.DistributedManagerService.1 Adding DATASYNC Permission Verification on the continuationManager API
4e41f4b71Sopenharmony_ci
5e41f4b71Sopenharmony_ciIn earlier versions, the **continuationManager** API does not verify the caller, which does not comply with the OpenHarmony API specifications.
6e41f4b71Sopenharmony_ciNow, before using **continuationManager**, the caller must apply for the **ohos.permission.DISTRIBUTED_DATASYNC** permission.
7e41f4b71Sopenharmony_ci
8e41f4b71Sopenharmony_ci**Change Impacts**
9e41f4b71Sopenharmony_ci
10e41f4b71Sopenharmony_ciThe application developed based on earlier versions needs to apply for the **ohos.permission.DISTRIBUTED_DATASYNC** permission in advance. Otherwise, the original service logic will be affected.
11e41f4b71Sopenharmony_ci
12e41f4b71Sopenharmony_ci**Key API/Component Changes**
13e41f4b71Sopenharmony_ci
14e41f4b71Sopenharmony_ciInvolved APIs:
15e41f4b71Sopenharmony_ci
16e41f4b71Sopenharmony_ci  - continuationManager.registerContinuation;
17e41f4b71Sopenharmony_ci  - continuationManager.on;
18e41f4b71Sopenharmony_ci  - continuationManager.off;
19e41f4b71Sopenharmony_ci  - continuationManager.unregisterContinuation;
20e41f4b71Sopenharmony_ci  - continuationManager.updateContinuationState;
21e41f4b71Sopenharmony_ci  - continuationManager.startContinuationDeviceManager;
22