A data processing job was started however it is still showing as not started. What is causing the delay in the job starting.
As a shared cloud service, it is possible for jobs on some days to have longer delays in starting than might otherwise occur.
Rarely will it do any good to open a support ticket, as by the time support is able to assign the case to an available engineer to research the issue, the job will start and complete.
Therefore we recommend that even if a job has not started, that you return later in the day to review progress.
Calling support typically does not result in speeding up data processing as if we killed the job and restarted it, the new job now goes to the back of the queue your job is already in, which only results in further delays. It is better therefore to give the system time to process the backlog of jobs that are queued.
Please remember this is a shared cloud service. While typically delays are short, on occasions long delays may be experienced.
Therefore it is always good planning to start your processes well ahead of any deadlines, and not at the last minute.
Delays can be more typical after release weekends, and planned or unplanned downtime when customer jobs are backlogged from after the downtime.
Also in peak season and during peak hours longer delays might be encountered. It is a good practice if possible, to run larger jobs during non-peak system usage.
If your job fails or the job still has not started after 8 hours, please open a support ticket and we will review server status.
Note: Support will not provide RCA's for delays experienced if the job ultimately starts but is just slow in processing. Please review our RCA policy for more details on when an RCA would be provided.
Example of jobs where a dealy might be experienced:
- CompSystemMassUpdate_UserImport - User data imports.
- Report exports
- Mass update of forms
- Mass launching of forms/worksheets
KBA , LOD-SF-CMP , Compensation Management , Problem