Hi,
We’ve had an issue with the inspection tool for a while. When inspecting a data point (type array) that enters a node, transform nodes, we see that the inspection tool only shows the first item in the array and we can not seem to reach the input data of the other array items, this makes it somewhat hard to debug.
Hi @XanderSchep,
Can you share the payload test and the capture of the datapoints?
Sure!
input:
My configuration:
If i want to debug the second item in the array in the inspection tool of the value setter, I only see the first item of the array instead.
now I can not get the input data for the second array item, if there is a fault in this items data. This makes debugging expansive data sets of attributes very hard at times.
Is this enough explanation?
Greetings
Xander
Hi @XanderSchep,
Thank you for the sample.
To see all data objects, click the first data point (near Nodes, Transform nodes). Here is the example:
Then, if you want to see directly which data has an issue, you can click on the data points of a Value Setter:
In your example, it only shows the first object in the array because all conditions match (no error), and you are clicking the data points of a value setter.
Clear! I just have 1 scenario in which this can still be quite timestealing. If you have a node, transform nodes with 10 data transformers in it to modify the datapoints. It fails in the 5th of those. you still have to manually input the data point you want to test out of the array into all of the 4 previous data transformers in the node,transform nodes to get the right input for your failed transformer. Is there also a trick to go around this?
Thank you in advance.
You can speed up the debugging a lot with this workflow:
If the error is in transformer #5, assume #1–#4 are OK
Since you already know the issue happens in transformer #5, it’s safe to assume transformers #1 to #4 are not causing the problem. So there’s no need to manually re-test each previous transformer step-by-step.
Fast-forward the input using “Execute transformer” (#1–#4)
Instead of copy-pasting the same array item through every transformer, use Execute transformer and select the transformers to execute:
#1 → #2 → #3 → #4.
Running this chain will give you the final payload output right after transformer #4.
Use that output as the test input for transformer #5
Take the output from step 2 and paste it into the test input of transformer #5.
This lets you debug exactly where the error happens, without repeating the earlier transformers.
If #5 errors, confirm via logs + inspection tool
When transformer #5 fails in the test:
Check the logs to see the exact exception.
Confirm the behavior with the inspection tool.
To find which array index is failing
Look at the first inspection datapoint (on Nodes, transform nodes).
That datapoint shows the complete array, so you can identify which item/index matches the failing case.
Inspect closer to the failing operation if needed
If you want a more precise view, open the inspection tool inside transformer #5 at the specific place where it fails (for example, in a value setter).
This helps you see the exact input reaching that failing step.
In short:
Run Execute transformer for #1–#4 to get the payload right before #5, test #5 directly, then use inspection + logs to pinpoint the failing array item/index
