As a Losant Developer, seeing how the payload updates and changes as data move through the workflow is time-saving to my development process. Today’s tip will show you how to do just that.
The Debug Node is the cornerstone of all workflows. Strategic use of the Debug Node is key when debugging workflows, so when developing workflows, seeing how the payload updates and changes as data moves through the workflow is critical to the development process.
Today’s Tip: Using the Debug Node’s configuration, you can change the Label, Property, and Output values in real-time to analyze and debug the payload.
The Debug Node can be renamed after the workflow has run a few times, and the name of the Debug Nodes in the Debug Panel will update, even for past payloads.
The Input and Output fields of the Debug Panel will also update in real-time. So, keeping track of a particular field in the payload can be done with ease. Or, if you’d like to retroactively see what a specific field looked like in past workflow runs (if there are still payloads in your Debug Panel), you can update the input and output fields to view how they looked previously!
The more and more I use the Debug Node, though, the more and more I’m impressed with the features it has. (For example, Copy Payload Path).
If you have any fun debugging techniques, we would love to hear them!