Troubleshooting errors - Data360_Analyze - 3.12

Data360 Analyze Server Help

Data360 Analyze
Product family
Product name
Data360 Analyze
Data360 Analyze Server Help
First publish date

If an error occurs when you run a node, for example if a node property has not been configured correctly, such as a syntax error, or if there is a reference to a field which does not exist, you will see the following node status icon:

Node with error

The Errors panel on the left side of the screen lists all node errors and warnings. For each node, the errors are listed in the order that they were generated, with the newest at the top of the list. Within the Errors panel, there are counts for the actual number of Errors, Warnings and Other errors.

In general, warnings are of lower severity than errors. Errors indicate the reason that a node has failed to run successfully, whereas warnings offer information about issues that do not prevent a node from running. For example, if you use the Excel File node to import a file with multiple worksheets but only have one output pin on the node, the node will run successfully, but only the first worksheet will be output. In this case, a warning would indicate that there are not enough output pins for the remaining worksheets.

Additional information that is listed when Others is selected includes node debug information, and errors that are generated by background compilation processes, relating to nodes which have not yet been run, or nodes that have had their status cleared. Temporary background errors may be generated by nodes which you have not yet fully configured.

  1. From the data flow canvas, hover over the red status icon on a failed node to display the error message in a tooltip. Alternatively, open the Errors panel to see a list of all errors and warnings. If you want to reduce the amount of information that is displayed in the Errors panel, you can hide warnings or other errors by clearing the relevant check box.
  2. From the Errors panel, select an error to focus the canvas on the node with the issue.

    With the Errors panel open on the left, you can display the Properties of a selected node on the right, allowing you to go through each of the failed nodes and correct any configuration issues before re-running the nodes.

    You can open the data viewer directly from the Errors panel by clicking the View data link and selecting a data set to view the data at the point that it errored.

  3. To display more detailed diagnostic information, such as error codes and stack traces, click View node log.

    The Node Log dialog opens, providing you with the following additional information:

    • A detailed summary of the selected node, including run information, the log path and the path for each data input and output. You can click the clipboard buttons to copy the paths.
    • A list of all errors and warnings, with full technical details. This information is useful if you need to speak to support about the errors that you are encountering.
    • Links to the input and output data of the selected node, where available, allowing you to troubleshoot the data in the data viewer.
    Tip: You can also open the Node Log dialog for a selected node from the Properties panel. The node summary information and links to node data are available for any node that has been executed.
  4. To download node logs and node data for further inspection, or for sharing with support, click Download.
    Note: If you do not see the Download button, please contact your administrator. If you are an administrator, please see Configuring node log download permissions.
  5. Select the items that you want to download from the Download Logs dialog, then click Download.

Required input pins

If a node requires a valid input connection to enable it to run, an orange circle is displayed within the required pin until an enabled input is connected. If a required pin does not have a valid input, the node will not be able to run, but in this case it will not error. If your data flow fails to run and does not show any errors, check to see if there are any required pins without valid inputs. For more details, see Connecting nodes.

Downloading server logs

When contacting support, it can help to provide as much information as possible. In addition to downloading node log information and node data, as described above, you can also download server logs:

  1. Click the Help button in the top right corner of the screen.
  2. Select About Data360 Analyze.
  3. Click Download Server Logs.
Note: On the server edition of the product, this button is only available to users with the role of Administrator.

Auto-fixing errors

Editing library nodes can cause errors in the data flows that use those nodes. The auto-fix functionality attempts to remedy the most common errors caused by library node editing. Examples of the types of errors that auto-fix can resolve, include:

  • Removing instances of deleted library nodes.
  • Removing properties or pins if they have been deleted from library nodes that are being inherited from.
If there are references to missing dependencies in your data flow, auto-fix typically removes these references. Therefore, before using auto-fix, we recommend that you first review the list of errors and, where possible, investigate the root cause of these issues, as restoring missing dependencies could be the correct resolution for some errors.
  1. Review the list of errors and, where possible, investigate the root cause of these issues.
  2. If you want to use auto-fix to automatically fix issues in your data flow, click Apply Auto-Fixes from the bottom of the Errors panel.
  3. In the Apply Auto-Fixes dialog, click the Apply Auto-Fixes button to continue.

    When the fixes have been completed, the Apply Auto-Fixes dialog shows a summary of the fixes that were applied.

  4. Click Close.