3666952 - Behavior of the calendar-based time sheet auto-submission job

This KBA explains the behavior of the calendar-based time sheet auto-submission triggered by TLMTriggerTasks job. 

SAP SuccessFactors Time Tracking

As per the blog Automatic Time Sheet Submission and Approval Capabilities in SAP SuccessFactors Time Tracking:
The processing carried out through the Time Recording Calendar is not done within the Submit Time Sheet job, but within the TLM Trigger Tasks job directly after the Submit Time Sheet job. 

The actual action of TLMTriggerTasks Job is to schedule a series of Time Management jobs based on the real-time system resource situation. 
So you may see some "time gaps" between the scheduled jobs, especially when the system resource is consumed by the whole data center workload.
For example, you may see the TLMTriggerRecalculation job (the first job to execute by TLMTriggerTasks job) is scheduled to run more than one hour later than the TLMTriggerTask job execution. 

This is expected behavior when the TLMTriggerTasks job run at a time of high workload which is also explained in KBA 2927303 - Change In Run Time Of Jobs Scheduled By TLMTriggerTask Job.

As a result, all the jobs triggered by TLMTriggerTasks job, including the calendar-based time sheet auto-submission, would happen several hours after the TLMTriggerTasks job execution.
This is expected and correct behaviour based on resource and load balancing mechanism.

Note: This is also why, by standard, it is always recommended only to keep one daily TLMTriggerTasks job scheduled to run at midnight time, when the system is least busy.
Multiple scheduling of TLMTriggerTasks job is NEVER recommended because of the risks explained in KBA 2705723 - Can Multiple Trigger Tasks Jobs Be Created or Scheduled at Custom Times?

If there is very special customer requirement to have TLMTriggerTasks job executed at a different time than 12AM of the Tenant Preferred Time Zone, and you experienced "delay" as explained above, you may consider below workaround to prepone the execution time of the jobs scheduled by TLMTriggerTasks job, including calendar-based time sheet auto-submission.
Note: This is only a workaround for the emergency situation. Please DO NOT use it as a daily routine. 

Triggering the TLMTriggerRecalculation job immediately will also prepone the whole job series, including calendar-based time sheet auto-submission, and this is possible by below steps from the Provisioning. 

1. Access "Manage Scheduled jobs". 
2. Choose Job Type: Trigger Recalculation. 
3. If you have not scheduled other recalculation job manually, the latest one should be scheduled by the daily TLMTriggerTask job. 
4. Click Run It Now. 
5. The TLMTriggerRecalculation job should execute immediately and also triggered the following jobs: 
   • timeSheetImportExternalTimes job
   • timeSheetGenerate job
   • timeSheetSubmit job

Note: The calendar-based time sheet auto-submission job log cannot be viewed from the Provisioning or the Execution Manager Dashboard. Please check the approval status of the concerned Employee Time Sheet directly. 

• KBA 2927303 - Change In Run Time Of Jobs Scheduled By TLMTriggerTask Job
• KBA 2738965 - Time Sheet Automatic Submission and Workflow Processing Behavior
• KBA 2705723 - Can Multiple Trigger Tasks Jobs Be Created or Scheduled at Custom Times?
• SAP Community blog: Automatic Time Sheet Submission and Approval Capabilities in SAP SuccessFactors Time Tracking
• SAP Help Portal Documentation: Creating a Calendar for Automatic Time Sheet Submission and Approval
• SAP Help Portal Documentation: TLMTriggerTasks Job

TLMTriggerTasks Job, trigger task job, trigger recalculation job, submit time sheet job, time recording calendar, time sheet auto submission, auto submit, tms, Employee Time Sheet, submit job, delay, time gap, scheduled run time , KBA , LOD-SF-TTR-TMS , Time Sheet , How To