Trigger Chain - Not completing
Udzielono odpowiedziI have recently created a new trigger chain or chain to run multiple other chains (in case the terminology doesn't fit), I created this by copying an existing trigger chain and change the parameters on which it runs. It runs as expected and all the chains that I expect to be run are triggered and the data is transferred, the issue I then have is that the trigger chain is continuously running and doesn't end, I have to stop this chain manually if I wish to re-run it. The error comes from the "Execute Chain" node and I get the below message in the LOGS. The only part of the chain that I changed was the parameter in the Query, is there something else that I should be updating?
Error executing transformation: path not found [0]
-
The partial error log indicates that you might be referencing a key in a JSON object that doesn't exist. Take a look at the input data coming into the node that is breaking and verify that the path is found in the data. If this doesn't help or resolve the issue, could you please provide the full log?
0Hi Jeff,
Unfortunately there isn't any more information in the error log, the chain will run for days and not crash. I copied this trigger chain from an existing chain and the only change I made was in the wording for which chains to include and also the name of the trigger chain, no other information was changed. I did not build the original chain so do not have all of the information but the set up is as below and only the final chain fails, as said all chains that should be triggered run correctly once and the data pulls through, it is just that the chain itself then doesn't stop.
0The Chain logic flow suggests that the "CSV to JSON (Copy)(..." node's JSON output is passed as input into the "Execute Chain (Copy)(..." node. The error "path not found [0]" suggests that the Execute Chain node is looking for a path in the JSON that is not found.
To verify this, look at how the Execute Chain node is configured, specifically how it is utilizing the JSON input. Then verify that value is in the JSON that is being generated in the CSV to JSON command. You'll likely find it is referencing a path that doesn't exist which is causing the error.
0Zaloguj się, aby dodać komentarz.
Komentarze
Komentarze: 3