Menu

XLSX scheduled job only contains 10k rows

ART Help
Aaron Eidt
2021-02-18
2021-05-27
  • Aaron Eidt

    Aaron Eidt - 2021-02-18

    I have a scheduled job that generates a xlsx file that should contain over 15k rows. Sometimes when the job runs it contains the correct number of rows, however most of the time it only contains 10k rows with the last row containing the string '...'
    The max rows for xlsx I have set to 250k and I also increased the default max rows from 10k to 20k in case that was causing it.
    When I run the report manually it contains the correct number of rows every time.

    Thanks!

     
  • Timothy Anyona

    Timothy Anyona - 2021-02-18

    Not sure what would be causing it. If you run the job manually from the jobs page do you always have the correct number of rows?

     
  • Aaron Eidt

    Aaron Eidt - 2021-02-18

    Yes I do. Just seems to be with the scheduled job

     
  • Timothy Anyona

    Timothy Anyona - 2021-02-18

    OK. Could you post your max rows specific setting.

     
  • Aaron Eidt

    Aaron Eidt - 2021-02-18

    Default max rows: 20000
    Specific Max Rows: xlsx:500000

     
  • Aaron Eidt

    Aaron Eidt - 2021-02-18

    Default max rows: 20000
    Specific Max Rows: xlsx:500000

     
  • Timothy Anyona

    Timothy Anyona - 2021-02-22

    Hi,
    I've uploaded a 5.3-snapshot file to the nightly folder. Please download and use that in a test environment. Create one job for the file in question and add a DEBUG logger for art.output.StandardOutput and then we can have a look at the logs when only 10k are produced.

     
  • Aaron Eidt

    Aaron Eidt - 2021-03-12

    I have been running the job with this version and have not been able to duplicate the problem. I recreated the job in my prod instance and still it randomly has the issue. Maybe I will delete the report and recreate it.

     
  • Timothy Anyona

    Timothy Anyona - 2021-03-12

    OK. Hope it gets resolved.

     
  • Aaron Eidt

    Aaron Eidt - 2021-05-27

    Just an FYI I have resolved this issue by increasing the JVM memory and memory of the OS.

     
  • Timothy Anyona

    Timothy Anyona - 2021-05-27

    Hi Aaron,
    Thanks for the note.

     

Log in to post a comment.