I have a few saved searches that query SQL DB via dbxquery and perform some calculations.
The search CRON schedule is set to */30 * * * *.
The dbxquery is something like :
SELECT top 20 * FROM tbl WHERE unitname LIKE '%integrated%' ORDER BY day DESC, shiftcode DESC
I have kept them as scheduled reports so that I can quickly check the cached results and not have to wait for the query to execute every time.
However, frequently the following happens:
This scheduled report runs on cron schedule */30 * * * *. Its time range is last 60 minutes. The following results were generated an hour ago.
This should not happen. As per the CRON exp., the results should always be generated less than 30mins back.
I have checked scheduler.log, the reports run successfully every 30mins as per the CRON exp. A sample event in scheduler.log for this savedsearch is as follows [I am masking some sensitive data with ***]:
The data that is generated is not refreshed as well. If I run the query manually, I get the refreshed data.
Please note that the time range for the search does not matter since we are not working on indexed data.
Is this something related to dbxquery, or am I missing out something?
We have encountered the same (a similar?) problem: The results shown under "reports" are not the most recent ones. We frequently see a sentence on top like "The following results were generated 7 days ago." while the most recent results were generated today (we can actually see them through "searches, reports and alerts" and clicking "View recent" for the correct scheduled search. This seems to be a bug of the "reports" view?
PS: We know for a fact that the data at the source db will mandatorily change within any 30mins period. Thus there is absolute zero chance of the data not getting refreshed due to no change in source data.