This issue may be seen in some instances after an upgrade. To correct this issue, go to the configuration page, make a change to the job and resave.
This should increase the timeout set for the job, so the job will be able to complete.
This issue has been seen when upgrading from earlier releases of TPAM, and was mentioned in the 2.5.917 Release Notes:
"If you are upgrading from 2.5.910 or lower and any of your scheduled jobs such as the Daily
Maintenance job, data extracts, scheduled backup, etc., have not been completing, after applying the
2.5.917 patch, go to the configuration page for the job and resave the job. This will increase the timeout
set for the job, so the job will be able to complete."
This has been seen in some instances after upgrading to other releases as well.