DataWorks:Troubleshooting missing instances

If you cannot find a task instance, this indicates that the instance was not created successfully. DataWorks creates instances to run task nodes based on the Instance Generation Mode and Scheduling Dependencies settings in the node's Scheduling Configuration. An instance may fail to be created for the following reasons:

• An instance cannot be created if the task node is isolated. A node is isolated if no Ancestor Nodes are configured in its Scheduling Dependencies. The instance will not appear in the instance list.

  This scenario typically occurs after you create nodes and workflows and then modify a node's dependency configuration. If you remove all of a node's configured Ancestor Nodes and then publish the change, the node becomes isolated and an instance cannot be generated.

• When Instance Generation Mode is set to Generate instance on the next day (T+1):

  • If you publish the task before 23:30, DataWorks creates the instance at 23:30 on the same day. You can find the instance on the instance list page in Operation Center the next day.

  • If you publish the task after 23:30, DataWorks creates the instance at 23:30 on the day after you publish it. You can find the instance on the instance list page in Operation Center two days after you publish it.

  If you check the instance list in Operation Center before the instance is created, you will not find the instance.

• When Instance Generation Mode is set to Generate instance immediately after publishing:

  Note

  Legacy workflows do not support setting Instance Generation Mode to Generate instance immediately after publishing.

  • If you publish the task after 23:30, DataWorks does not create an instance. In this case, you cannot find the instance in the instance list.

  • If you publish the task before 23:30, DataWorks creates the task instance immediately. You can find the instance in the instance list.

    • If the scheduled runtime is more than 10 minutes after the publishing time (for example, published at 18:00 and scheduled to run at 18:30), DataWorks creates the instance and runs the task normally. You can find the instance in the instance list.

    • If the scheduled runtime is less than 10 minutes after the publishing time (for example, published at 18:00 and scheduled to run at 18:05), DataWorks generates a completed instance. The property of the node instance is set to expired real-time instance.

  In this scenario, if you publish the task after 23:30, you cannot find the instance. However, if you do find an instance, check whether it is an expired instance.