Is there any way to trace PREVIOUS executions of a piston? I have a number of pistons where the trace function doesn’t work well because there are waits involved, which means the piston goes to sleep and starts up later to finish a task. If there is no way to do this I would suggest it be considered for a future upgrade. It is so easy to see what was missing when a piston fails if I can look at the traced output, rather than trying to step through the logs.
Cordell Jeppsen
I often set my logs to "Minimal’ and then write code in the piston to make my OWN logs happen at various spots throughout the execution. It can effectively catch anything that you code for, and will be much less clutter to wade through… (plus it will be in plain English!)
Theoretically, you can set your logs to ‘None’ for an even cleaner log, but when it’s set to ‘None’, it usually clears the log each time you edit the piston. (which is why I am recommending ‘Minimum’)
In addition to what @WCmore stated, using the LOG TRACE option will always insert your comments to the log display, even with log set to NONE.
Very true. (just remember that editing that piston will clear all logs if it’s set to ‘None’)
An advanced version of this is setting your custom log as either ‘Warning’ or ‘Error’. The different colors make your personalized logs stand out a bit from all the mumbo-jumbo.
Here is all 5 colors for reference:
