This article demonstrates the use and functioning of the Logger in a journey.
What you'll need:
Skill level: Easy
Time required: 5 minutes
- Drag and drop data pills from the Data Tree Output you want to log
- Basic level of analytical skills to look for errors
Know the use of a logger and implement it in a journey
You can click the following preview to watch a video of this article or continue with the guided walk-through:
What is a logger:
Logger by Quickwork lets you record the input/output of a trigger and previous actions while a journey is in the execution state. This tool is useful to visualize the complete set of data flowing amongst each action through which you can debug the journey process, in case of unexpected results. By studying the logged response, you can also backtrack to each action step where you believe a small tweak in the inputs would give you better results.
Why is it needed:
Consider, an IT company has all your connectors' code deployed on the GitHub repository. The developers are working on them to make it public. At the same time, they are maintaining a Goggle Sheet containing the details of each connector along with its deployment status i.e. Pending, In Progress, QA, Done, etc. and the assignee details. Right from the Pending status to Done, the connector deployment task gets moderated rigorously. If any task lies in the Pending state for more than 24 hours, the assignee gets an escalation email from the manager reminding him/her to complete the due.
While executing the above-mentioned journey, if an unexpected result pops up, it becomes difficult to find the pain point as the error could be in GitHub, Google Sheets, Scheduler, or Gmail app. This situation is perfect for Logger.
How to use it:
- Under the Steps section and choose Logger in the App field.
- Select the action, Log a Message, from the drop-down menu in the Action field.
- Now drag and drop Logger under the action of which data (I/O) you want to log.
- As soon as you place Logger at a specific position under a specific action, e.g. Google Sheets, you'll see the output keys of Google Sheets and all the actions configured above Google Sheets.
- In the Message input field of Logger, you can pass the data pill of which records you want to log.
- Give a name to this logger step in the Step Name field:
Now whenever you run the journey, you can see a complete set on input/output data of a logged action. By referring to this, you can correct the inputs specified and troubleshoot the complete journey or manipulate the in-app data manually.
Below is the example of Logger output. The prior action used in the journey was Google Sheets to which the input was the column-header of the sheet in which the details of connector deployment status were stored. In the example, there was a huge list of connector details.
By using the Logger at this point, the data can be read more precisely as it logs the complete information that Google Sheets hold. Due to this, the troubleshooting of the journey could be done easily if you were expecting some status of the connectors to be Done instead of Pending:
By this, you'll get an idea to change the data manually in Google Sheets or any other actions you intend.
Note: You can use Logger for each action configured in your journey.