Common Data Workflow Errors

The Data Workflow component lets Creators build complex logic and transform data in an application. Because of its flexibility, configuration issues can occur.

The Build Agent can help diagnose Data Workflow issues quickly. Describe the unexpected behavior in the agent chat before working through the steps below.

Apply the investigate, isolate, and terminate approach when troubleshooting a Data Workflow. For a full explanation of each step, see Troubleshooting Unqork Applications.

Isolating Data Workflow Issues

When narrowing down the cause of a Data Workflow error, begin with these questions:

1. Is the Data Workflow running?

   The Data Workflow must be triggered to run. When the trigger type is set to Watch, it triggers automatically. If set to Manual, it must be triggered manually; a Button component can serve as the .

2. Do all required inputs have non-zero values?

   Zero-value inputs are one of the more common pitfalls in Data Workflows. Inspect the Data Workflow's DevTools Console. If a circular reference error is present, it displays after triggering.

3. Are the expected input values visible in the DevTools Console when the Data Workflow is triggered?

   Attach Console operators to each Data Workflow operator, beginning with the inputs and working toward the outputs, to pinpoint where the issue occurs. Remove Console operators when troubleshooting is complete.

4. Is the output operator configured with the correct action?

   Each pipeline must end with an Output or Set Outputs operator. If the action type doesn't match what the target component expects, the pipeline runs without error but the component doesn't update. Confirm the action type and attach a Console operator to the output port to verify data is reaching it.