Help Center/ DataArts Studio/ FAQs/ DataArts Factory/ Why Is There a Large Difference Between Job Execution Time and Start Time of a Job?

Updated on 2024-08-30 GMT+08:00

View PDF

Why Is There a Large Difference Between Job Execution Time and Start Time of a Job?

Symptom

On the Running History page, there is a large difference between Job Execution Time and Start Time. Job Execution Time is the time when the job is expected to be executed. Start Time is the time when the job starts to be executed.

Possible Causes

In Data Development, a maximum of five instances can be concurrently executed in a job. If Start Time of a job is later than Job Execution Time, the job instances in the subsequent batch will be queued.

Solution

If you find that the difference between Job Execution Time and Start Time becomes large, adjust Job Execution Time accordingly.

Parent topic: DataArts Factory

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot