https://community.cloudera.com/t5/Support-Questions/Oozie-skipping-action-as-coordinators-instance-getting/m-p/181436#M143653 <P>off late i am seeing this issue in oozie , where the instance of a coordinator is getting kicked up after the (next materialized time) , for e.g if the coordinator was scheduled to start next action at 10 AM its only starting may 30 mins post that , and because of that it just creates the action and marks it as skipped with message <STRONG>current time is later than the nominal time of the next action</STRONG></P><P><STRONG><BR /></STRONG></P><P><STRONG>Question : Why is oozie not creating the action when it should ? </STRONG></P><P><STRONG>I have checked CPU utilization and memory utilization of server thinking server unable to trigger the action but server stats looks good ( CPU under 50 , memory under 20 %)</STRONG></P><P><STRONG><BR /></STRONG></P><P><STRONG><BR /></STRONG></P><P>2018-01-08 13:55:58,572 INFO org.apache.oozie.command.coord.CoordActionInputCheckXCommand: SERVER[xxxxxxx.internal] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0014607-171123123643404-oozie-oozi-C] ACTION[0014607-171123123643404-oozie-oozi-C@299] LAST_ONLY execution: Preparing to skip action [0014607-171123123643404-oozie-oozi-C@299] because the current time [2018-01-08T13:55Z] is later than the nominal time [2018-01-08T13:55Z] of the next action]</P><P>&lt;coordinator-app name="${co_pend_publish}" start="${startTime}" end="${endTime}" timezone="${timezone}" frequency="${pend_pub_coord_frequency}" xmlns="uri:oozie:coordinator:0.2"&gt; &lt;controls&gt; &lt;timeout&gt;${pend_pub_coord_timeout}&lt;/timeout&gt; &lt;execution&gt;LAST_ONLY&lt;/execution&gt; &lt;throttle&gt;1&lt;/throttle&gt; &lt;/controls&gt; &lt;datasets&gt; &lt;dataset initial-instance="${startTime}" name="publish_flag" frequency="5" timezone="${timezone}"&gt; &lt;uri-template&gt;${dataRoot}/publish&lt;/uri-template&gt; &lt;done-flag&gt;${publish_manifest}&lt;/done-flag&gt; &lt;/dataset&gt; &lt;/datasets&gt; &lt;input-events&gt; &lt;data-in name="publish_flag_event" dataset="publish_flag"&gt; &lt;start-instance&gt;${coord:current(0)}&lt;/start-instance&gt; &lt;end-instance&gt;${coord:current(0)}&lt;/end-instance&gt; &lt;/data-in&gt; &lt;/input-events&gt; &lt;action&gt; &lt;workflow&gt; &lt;app-path&gt;${automationAppRoot}/workflows/${wf_dir_name}&lt;/app-path&gt; &lt;configuration&gt; &lt;property&gt; &lt;name&gt;nameNode&lt;/name&gt; &lt;value&gt;${nameNode}&lt;/value&gt; &lt;/property&gt; &lt;property&gt; &lt;name&gt;jobTracker&lt;/name&gt; &lt;value&gt;${jobTracker}&lt;/value&gt; &lt;/property&gt; &lt;/configuration&gt; &lt;/workflow&gt; &lt;/action&gt; &lt;/coordinator-app&gt;</P> Wed, 10 Jan 2018 07:37:13 GMT deviojha09 2018-01-10T07:37:13Z