K22.1, most users using classic screens
We have a BAQ that, if users forget to enter a part number, can return millions of records and we believe a user may have done this, and force-terminated the smart client due to it taking so long. Perhaps the same person would log in again, and try it again.
We are already taking steps to change the query so it won’t run without a part number specified. My question is, in the situation described, how long would the BAQ continue to run, consuming server resources, after the user’s session was forcibly terminated?
Best answer by hburkeView original