forked from docs/doc-exports
Xiong, Chen Xiao
f3ee29a3dd
Reviewed-by: Rechenburg, Matthias <matthias.rechenburg@t-systems.com> Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Xiong, Chen Xiao <chenxiaoxiong@huawei.com> Co-committed-by: Xiong, Chen Xiao <chenxiaoxiong@huawei.com>
18 lines
1.5 KiB
HTML
18 lines
1.5 KiB
HTML
<a name="dataartsstudio_03_0111"></a><a name="dataartsstudio_03_0111"></a>
|
|
|
|
<h1 class="topictitle1">Why Is There No Job Running Scheduling Record After Daily Scheduling Is Configured for the Job?</h1>
|
|
<div id="body0000001105111928"><div class="section" id="dataartsstudio_03_0111__section14911347184712"><h4 class="sectiontitle">Symptom</h4><p id="dataartsstudio_03_0111__p173204526470">Daily scheduling is configured for the job, but there is no job scheduling record in the instance.</p>
|
|
</div>
|
|
<div class="section" id="dataartsstudio_03_0111__section4211313162610"><h4 class="sectiontitle">Cause Analysis</h4><p id="dataartsstudio_03_0111__p135237112611">Cause 1: Check whether the job scheduling is started. If not, the job will not be scheduled.</p>
|
|
<p id="dataartsstudio_03_0111__p125163718262">Cause 2: The instance query time range is too long. If a dependent or self-dependent job is configured, check whether the historical job instance is waiting for running due to the dependency failure. As a result, no new job instance is generated.</p>
|
|
</div>
|
|
<div class="section" id="dataartsstudio_03_0111__section19140174714388"><h4 class="sectiontitle">Solutions</h4><p id="dataartsstudio_03_0111__p1418816477386">Configure Job exception alarms and instance timeout duration. When the waiting time exceeds the instance timeout duration, the system sends an alarm notification.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dataartsstudio_03_0035.html">DataArts Factory</a></div>
|
|
</div>
|
|
</div>
|
|
|