veetmoradiya3628 opened a new issue, #8467:
URL: https://github.com/apache/incubator-devlake/issues/8467

   ### 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
   
   Hi DevLake Team,
   
   I'm facing an issue where I have configured my blueprint to run daily and 
selected a 6-month range from the date of configuration, so it has set that 
timestamp for the timeAfter parameter.
   
   Now, although my pipeline is running daily, the data is not getting updated 
for the current date. It still considers the time frame as from the timeAfter 
(6 months back from the configuration date) to the configuration date.
   
   ### What do you expect to happen
   
   I am expecting that if i have configured the 6 month or 1 year time then it 
should consider current date to current date - 6 month or 12 month based on 
configuration.
   
   For example 
   For one of my blueprints, I enabled it on 10th June 2025, so it correctly 
set the timeAfter parameter as 10th December 2024 to 10th June 2025, which is 
expected.
   
   Now, I had a few deployments on 11th and 12th June 2025. Even though the 
pipeline is configured to run daily and the runs are successful, it is still 
not picking up the deployments from 11th and 12th June.
   
   Devlake UI
   
   
![Image](https://github.com/user-attachments/assets/7e1b5bbb-7e57-4677-a465-633e9924188a)
   
   Grafana UI
   
   
![Image](https://github.com/user-attachments/assets/52ac833d-aa85-457b-b8f8-c10cf041b4fa)
   
   ### How to reproduce
   
   Steps mentioned above.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   devlake:v1.0.2-beta8
   
   ### Are you willing to submit PR?
   
   - [x] 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: dev-unsubscr...@devlake.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to