How are time limits enforced and managed?
If a user runs a report that takes too long, which process terminates it, and why is this necessary?
7 replies
- You must be logged in to reply to this post.
Sign in with LinkedIn or Google to take part.
Home › Discussions › Questions & Answers › How are time limits enforced and managed?
Customer · · Questions & Answers · 7 replies
If a user runs a report that takes too long, which process terminates it, and why is this necessary?
The termination is handled by the ‘Blitz Report Monitor’ concurrent program. This is necessary to automatically cancel reports exceeding the set time limit, which prevents excessive server load, especially if a report was submitted with insufficient parameter restrictions.
How often should the Monitor program be scheduled?
If you are actively using the time limit feature, it is recommended to schedule the Monitor program frequently, for example, every 5 minutes. Reports will continue running until the Monitor ‘wakes up’ to stop them.
Does the Monitor program perform other tasks besides canceling long-running reports?
Yes, it performs several critical cleanup tasks. These include marking terminated or error report runs as *complete*, purging outdated log data and SQL history, and removing inactive users from the Blitz Report license user table.
If we don’t use the time limit feature, can we schedule the Monitor less often?
Yes, if the time limit feature is not used, a longer schedule, such as daily, can be set up. This still ensures the other essential cleanup and administrative actions are performed.
Sign in with LinkedIn or Google to take part.