How to solve when Save Incorta fails with “Invalid Token ” error

General
1

Problem

Some users have reported that the Save Incorta node fails with an error like:

Invalid Token [1234abc-xyza123.......]

This has been observed after workflow changes, including cases where the workflow produces multiple outputs.

  • The error occurs at the Save Incorta node.

  • The workflow execution completes up to that point.

  • The error message includes a UUID “token.”

  • The workflow may return multiple output DataFrames.

Important note about multiple outputs

When a workflow produces multiple outputs, programmatic execution returns a map of output DataFrames.

You must explicitly select the intended output by key:

val outputDataFrames = WorkflowExecuteInIncorta.executeWF(...)
val output_df = outputDataFrames.get("Expected_Output_Name")

If the wrong output (or no output) is passed downstream, Save Incorta may fail.

Troubleshooting Checklist

  1. Confirm the correct output DataFrame

    • Ensure Save Incorta is connected to the intended output branch.

    • If executing programmatically, extract the correct DataFrame by key.

  2. Check workflow structure

    • Verify that Save Incorta receives a valid DataFrame.

    • Confirm no branches are unintentionally disconnected.

  3. If the workflow was imported

    • Ensure the connection used by Save Incorta is correctly mapped by name.

Summary

The “Invalid Token” error is a runtime Save Incorta issue.

The best approach to solve is:

  • Validate output selection

  • Verify workflow wiring

  • Review logs

  • Confirm connection mapping if imported