Are there any best practices out there for how long an NSQ file runs? We have some in production that run 8+ hours and my guy tells me that's not good for anything but I also can't think of a way to speed to running through all rows for a filter.
I have worked with applciations that have taken many hours to run. To ensure the applciation is actually running, you can swith over to the qvw and see that the tabs are changing (you would need to do this from whereever the nsq is running - it could be run from a task on your desk top or through the server, but either way, it brings up a local qlikview app)
When they run this long, it is usually the result of a combination of filters, levels, and page breaks - the more combinations it has to createm, the longer it will take
were you able to successfully run the applciation with a filter on the report to limit the run