Utility Session Management - It's Inside the Database in Teradata 13.10! (UPDATED) - comment by carrie

Raghav,
If you relying on MaxLoadTask to  manage the concurrency of utility jobs, you will never get the delay option.  When MaxLoadTask finds that a new load utility job would exceed the limit for MaxLoadTasks, it will reject that job.  It does not have the ability to delay
 
If you want the delay option, try using Utility Throttles, ot if you are on 13.10 for both the database and the client then internal default throttles will delay even if you are not using utility throttles.  Once you have utility throttles defined, MaxLoadTask will be ignored.  You can specify that you want the delay option on the screens that allow you to define utility throttles.
 
Another reason for not getting a delay action when you expected to is if you are using non-conforming utilities, which will only be able to reject.   Non-conforming utilities are non-Teradata utilities that do not use the TPT API, but instead rely on their own legacy CLI interfaces.  Most current releases of non-Teradata utilities tend to use the TPT API, so should be able to delay, but you would have to double check that.  
 
Tenacity and sleep settings will not have an impact on whether or not a load job is delayed or rejected.  Tenacity only plays a role if a job has already been rejected and the client software sees that rejection.  If the job is delayed, it stays under the control of TDWM in the database and will no longer be under the control of the client.  
 
Thanks, -Carrie