klesh opened a new issue, #4529: URL: https://github.com/apache/incubator-devlake/issues/4529
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement. ### Use case Records were deleted from the data source side and users want them gone in DevLake while keeping the time filter unchanged ### Description Currently, we have `diffSync` activated by default without any user intervention, it works fine in most scenarios, however, records might be deleted from the Data Source but still exist in the DevLake database no matter how many times they try to recollect data due to the limitation of the `diffSync`. To force a data refresh to remove those records, one would have to push the time filter to an earlier time to trigger a Data Purge Procedure to make things right, this is unintuitive and ugly. We should design a Flow to allow users to Refresh Data explicitly. ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
