5 Replies Latest reply on Dec 6, 2013 10:23 AM by Russell Christopher

    tabcmd timeout still times out at 21,600 seconds?

    Glen Park

      Hey everyone,

       

      Hopefully this is a simple answer...I'm attempting to use tabcmd to call an extract refresh that currently times out at the max of 6 hours (21,600 seconds) by setting the "--timeout" parameter to 10 hours (36,000 seconds) so that it can have a chance to complete.  I executed it and it successfully queued up in the background tasks monitor and proceeded to extract....then promptly timed out again at the 6 hour mark.  Does the timeout parameter for the refreshextracts tabcmd have a limit as well??  I thought this would override what's set by default on the server for a single job (as I would like to avoid resetting the default timeout at the server level). 

       

      Any help is appreciated.

       

      Thanks!

      Glen