Finding a Step in the Debug Log

This article is intended to be a short supplementary how-to for our larger Logs and Debugging documentation, and it’s recommended that you take a read of that document to fully understand how to use and navigate Tray’s logs. 

There are a lot of options when searching the debug logs, and it can be easy to get lost when you’re trying to find one specific step if you have a large or complex workflow. 

The simplest thing to do in most cases if your aim is to find a given step is to use the Successful search option, then select the step name you’re looking for. It’s important to remember to click the magnifying glass icon to commence the search!

You can also combine queries, such as searching for failures and successes for a step before a given date/time. 

If you still don’t find it, the step may have failed, the execution may have failed at an earlier step, or your log may have expired. On most plans, logs expire after thirty days. You may also get no result for a given step if the workflow hasn’t been run with that step yet, which can happen in cases where the step is a new addition, or is part of a boolean or branch that may where that option hasn’t been taken in any execution.