GitHub user dosubot[bot] edited a comment on the discussion: What is the meaning of setting custom value for Time Range in "Set Sync Policy"
<!-- Answer --> Setting a custom Time Range in "Set Sync Policy" defines the earliest date from which DevLake will collect data during syncs. This Time Range acts as the starting point for the initial historical data collection window. After the first successful sync, DevLake switches to incremental syncs, using the last successful sync time as the new lower bound for future data collection, not the original Time Range start date. So, the Time Range is mainly relevant for the first sync or if you reset the sync policy to an earlier date [source](https://github.com/apache/incubator-devlake/blob/2c15ad880dce830c6512fa58039527cbf4745b8b/backend/helpers/pluginhelper/api/collector_state_manager.go#L29-L119). For most data sources (like PRs), the Time Range filter is applied to the creation time. This means if you set the period to 3 months, PRs created more than 3 months ago but merged now will not be collected by the main collector, because their creation date is outside the window [source](https://github.com/apache/incubator-devlake/blob/2c15ad880dce830c6512fa58039527cbf4745b8b/backend/plugins/azuredevops_go/tasks/pr_collector.go#L65-L74). However, DevLake has a secondary mechanism: if incremental sync is enabled and the plugin supports it, there is a secondary collector that can pick up updates to "unfinished" or recently updated records (like open PRs), even if they were created before the Time Range. This helps capture late merges or updates, but only for records that are still open or have recent activity [source](https://github.com/apache/incubator-devlake/blob/2c15ad880dce830c6512fa58039527cbf4745b8b/backend/helpers/pluginhelper/api/api_collector_stateful.go#L30-L269). Here's a simplified diagram of the sync logic: ```mermaid graph TD A["Set Time Range (Start Date)"] --> B["First Sync: Collect data created after Start Date"] B --> C["Incremental Syncs: Use last successful sync time as new lower bound"] C --> D["Secondary Collector: Picks up updates to old records if supported"] ``` If you want to ensure you capture late updates to old PRs, consider setting a wider initial Time Range or check if your plugin supports the secondary collector for unfinished/updated records. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fincubator-devlake).* --- Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fincubator-devlake). [](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fincubator-devlake#message_id=8a10e72f-d666-48d9-86c4-55f58123fbed) [](https://github.dosu.com/apache/incubator-devlake?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fincubator-devlake) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fincubator-devlake) GitHub link: https://github.com/apache/incubator-devlake/discussions/8663#discussioncomment-15276175 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
