SushmitaMahapatra23 opened a new issue, #7886: URL: https://github.com/apache/incubator-devlake/issues/7886
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened The timeAfter parameter in the DevLake sync API isn't functioning as expected; it's using the time range configured in the config-ui instead. ex: ``` curl -X 'POST' 'http://localhost:4001/api/rest/blueprints/4/trigger' -H 'accept: application/json' -H 'Content-Type: application/json' -H 'Authorization: Bearer <token>' -d '{ "fullSync": true, "skipCollectors": false, "skipOnFail": false, "timeAfter": "2024-08-11T05:00:00Z" }' ``` ### What do you expect to happen The timeAfter value provided in the API parameter should take precedence over the default timeRange in DevLake. ### How to reproduce ``` curl -X 'POST' \ 'http://localhost:4001/api/rest/blueprints/4/trigger' \ -H 'accept: application/json' \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer <token>' \ -d '{ "fullSync": true, "skipCollectors": false, "skipOnFail": false, "timeAfter": "2024-08-11T05:00:00Z" }' ``` **Monitor the sync process and observe whether it respects the timeAfter parameter you provided. Verify if the sync is using the time range from the config-ui instead.** ## Expected Behaviour **The sync process should respect the timeAfter parameter provided in the API call and use "2024-08-11T05:00:00Z" as the starting point.** ## Actual Behavior **The sync process ignores the timeAfter parameter and uses the time range configured in the config-ui.** ### Anything else _No response_ ### Version v0.17.0-beta2 ### Are you willing to submit 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]
