3 Replies Latest reply: Sep 20, 2016 5:37 PM by Cassandra Baqir RSS

    NP16 Scheduler Issues

    Cassandra Baqir

      Hoping to find some advice for a couple issues.


      1. I have a report schedule to run on Tuesdays at 8:15am but for some reason the report ended up running at 5:15pm on the same day. The time zones for the QV Server and NP monitor are correct. Any other ideas where this could be happening?


      2. We have many reports that run every week - some that take a couple of minutes and some that take several hours. What is the best way to manage NSQ execution by triggers (wgen A completes, B kicks off) to avoid reports overlapping and thus not running?


      3. How do we avoid reports running for several hours when the data set is very large?



        • Re: NP16 Scheduler Issues
          David Ganly

          hi, I have certainly seen issue one happening before.  ran Windows update on NP server machine and restared, problem went away so didn't dig deeper into the problem.  i have also backed up the scheduler.xml and allow it to be recreated automatically to fix another problem where jobs were not running at all.


          on item 2 I have a number of tasks that have dependencies with each other so I set them up as individual tasks and sequence them within the same job (use the uptown arrows) so the order in which they execute ensure the dependencies are fulfilled.


          hope this helps

            • Re: NP16 Scheduler Issues
              Samuel Bazaldua

              1. How many scheduled reports are setup to run on that day? If you have multiple reports that start running from 6 am-8:15 am and some of these take a while to complete then the next scheduled job will be delayed before it can begin and so on. This is due to single threading in NP16. Only one scheduled job at a time can complete before the next one begins.

              2. I agree with David and use this process as well. It is important to try and time your schedule out for reports as you suggested ( When A completes, B kicks off)

              3. There are a number of factors as to why a report can run long. For one nsq you may have 10 scheduled tasks with independent filters, emailed users, etc for each one. So these jobs take longer. I typically run these reports late at night or early in the morning when other smaller jobs are not run. If you have an environment with multiple NPrinting servers then positioning/timing your reports on different servers is much easier to manage. This is one area where NP 17 should help since it is multi-threaded environment.

              • Re: NP16 Scheduler Issues
                Cassandra Baqir

                Let me rephrase #2. In QV, I have triggers so my files reload once the QVD refreshes, for example. I want all of my nsqs to be set so that the completion of a file triggers the next file in the list. I am not sure how to automate this.