Refresh report

Hello,
One answer

Hi lidia,
It depends on what kind of report you are using...
If it is the report using Data Warehouse, I think it is working as designed, because you need to run data collection job (ETL) to load the changes into the DW. So there is a time gap to refresh the data (usually up to 24 hours, depending on how frequently you run this job). You may add the frequency how often you run data collection job, but careful planning is required, as it may add significant workload into both report server and CLM server.
If you are running a report using Lifecycle Query Engine (LQE), it is almost real time (refreshed every minute by default), so this problem should not happen. This is the better option if you need real time report.
Comments

ok, thank you.

Go to https://[servername]:9443/dcc/web > Data Collection job. Click on Schedule and Interval Schedule. You can set the interval of DCC job schedule.
Do not set too small number here. If the subsequent job starts before current job finishes, then eventually the scheduling will gets jammed. Monitor how long DCC job takes in the busiest time, and set higher number than this. Either way I doubt it will be as closed as real time, so I am not sure if DWH is the solution for you.