topic Re: Debugging in Workato in Workato Pros Discussion Board

Debugging in Workato

gajanan-patil — Wed, 12 Jan 2022 19:22:29 GMT

Hello Team i am trying to work on best practices as of now and while i am doing that can you please help us out with how are we going to check Debugging in workato. As of now we are having Monitor and On Error Retry but is there anything else to debug step by step in workato platform ,thanks in advance !

Re: Debugging in Workato

veeravenkatasat — Wed, 12 Jan 2022 19:40:44 GMT

Hi Gajanan, Currently we don't have step by step debugging available in workato. You go with Monitor block and see the error message if any failures inside recipe.

use log message or look up table to see the loop data or any specific data.

Re: Debugging in Workato

jayesh — Wed, 12 Jan 2022 23:58:42 GMT

Hi Gajanan,

For each recipe job you can see the actual call flow path as well as the input and output at every step. If the recipe job failed - you can see the call path till the error step and the input, output at every step and the error at the error step. Here is the link to the documentation section for troubleshooting: https://docs.workato.com/troubleshooting.html#troubleshooting

Re: Debugging in Workato

dcornwell — Thu, 13 Jan 2022 02:13:29 GMT

I heard in the past that there is an enhancement coming so you can view job data from inside loops without having the hassle of setting up logging. This is sorely needed but I don't know if it's still coming or when. This is something I've been pushing for a long time.

Re: Debugging in Workato

wvkashif — Thu, 13 Jan 2022 12:48:19 GMT

I would recommend using Job Table Dashboard for faster debugging purposes.

Say if your recipe's goal is to pin a message in slack channel. Without actually going to the job details; your job table should be able to say what happened with that job..

For eg. I would use the following fields- slack channel Name; MessagePinned? (boolean);

Along those lines

Re: Debugging in Workato

gwilkinson — Thu, 13 Jan 2022 20:52:30 GMT

I heard the same and believe it is still on the roadmap

Re: Debugging in Workato

gwilkinson — Thu, 13 Jan 2022 20:56:35 GMT

I use the Stop action along with Repeat to accomplish step by step execution and verification of step-level results. Also, the Skip Steps is useful while debugging, as is Logger by Workato.

Re: Debugging in Workato

steven-marissen — Thu, 13 Jan 2022 23:25:42 GMT

When a lot of actions are needed (item level), I usually add results first to a (nested) list, as a sort of "preparation" step. Then further down the recipe I do the actual updates for each of those records in the list (example update Salesforce opp).

For me it is often easier to troubleshoot what happened as you can't go through every iteration of a repeat action.

Sometimes I also make use of a validation loop (between creating the list and doing the update). To make sure if it is valid before executing.

Hope this gives you some ideas to try out.

Re: Debugging in Workato

gabriel-sim — Fri, 14 Jan 2022 13:41:06 GMT

Hi Gajanan, apart from all the brilliant solutions in this thread, we are currently in the early stages of building a feature that will allow you to try out each action as you build your recipe. Think of it as something similar to the HTTP action wizard.

Would that achieve what you are looking for?

Re: Debugging in Workato

gwilkinson — Fri, 14 Jan 2022 20:52:11 GMT

Agree, I customize the Job Table with key run-time information. It is quite helpful for a quick view of results for each job, and I can then drill into speciffic jobs based on what I see on the Job report.

Re: Debugging in Workato

lcury — Sat, 15 Jan 2022 05:31:32 GMT

On top of that, I've learned that for a failed job, once you repeat it, you can then select the step you'd like more information and go to "Debug" tab.

If available, the Network Trace will include all API calls during that step, with the result, header, request and response payloads.

Very helpful, specially if you're using a connector where the input for that action is not necessarily the actual payload that will be used in the API call.

I wish that this Debug information would have been available by default at the very step in which a job failed. Some times, it's just not feasible to repeat a job, depending on how your recipe is designed and particularly if that's in a Production environment.

Re: Debugging in Workato

gajanan-patil — Mon, 17 Jan 2022 19:00:14 GMT

Hi Gabriel,

The above solutions are great to start with , and i would love to see new features as they will lead to recipe optimization. Thank you so much Everyone !