Klasyczne typy plików nie są już dostępne od stycznia 2021 r. Możesz przenieść swoje klasyczne pliki lub pobrać plik PDF. Dowiedz się więcej

Trigger Chain - Not completing

Udzielono odpowiedzi
0

Komentarze

Komentarze: 3

  • Jeff Hickey

    Hi Christian Hanbury,

    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?

    0
  • Christian Hanbury

    Hi 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.

    0
  • Jeff Hickey

    Hi Christian Hanbury,

    The 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.

    0

Zaloguj się, aby dodać komentarz.