What is a one sentence summary of your feature request?
“RUN NOW” Option for “state-in-time” Reports
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
The “state-in-time” reports are intended to record system configuration values. However, after modifying system settings, the “state-in-time” reports often take 1–2 days to reflect the changes. As a result, during audits or product demonstrations, customers are unable to immediately reflect the updated configuration status.
In addition, the generated “state-in-time” reports are sometimes inaccurate and inconsistent from day to day. This issue has already been reported under support ticket #00452284. When the report content is incorrect, there is currently no option to re-run the report, requiring customers to wait until the following day to verify the results.
Therefore, we would like to request the addition of a “RUN NOW” function within the “state-in-time” feature.
How do you currently solve the challenges you have by not having this feature?
This issue raises serious concerns among customers regarding the accuracy of the report content. Moreover, when they have to wait 1–2 days for the reports to update and still encounter incorrect results, it significantly impacts their work efficiency.
Thank you for your detailed request. We understand the challenge you are facing with the latency and occasional inconsistencies in “state-in-time” reports.
Per product design, “state-in-time” reports are generated during scheduled data collection cycles. These cycles are optimized for performance and storage considerations, which is why changes to system configurations may not be reflected immediately. Currently, there is no mechanism to trigger on-demand regeneration of “state-in-time” reports, as they rely on the most recent collected snapshot.
Your proposal for a “RUN NOW” option is valid and would provide clear value in scenarios such as audits, product demonstrations, and validation of recent configuration changes. This enhancement would allow customers to bypass the wait for the next collection cycle, directly addressing concerns about timeliness and accuracy.
To evaluate feasibility, we will need to analyze how a manual trigger could integrate with existing data collection logic without compromising performance or report integrity. Additionally, we will review the linked support case (#00452284) to ensure that the reported inconsistencies are investigated in parallel, as data accuracy is a critical prerequisite for this functionality.
We appreciate your input and will log this as a feature request for consideration in future roadmap planning.