1) Give a description of the problem
I have a Piston where the Trace Toggle is sometimes there, sometimes not (usually not). This is the only Piston I have in this condition. The Piston does not subscribe to anything, but I have other Pistons that don’t as well, they have Trace Toggles.
Hi, I’ve tested it dozens of times. Sometimes the toggle shows up, but then disappears again. Usually it’s not there. When you say set it up to execute do you mean add a trigger so something other than test executes the piston? Right now it’s not subscribed to anything. Note that I’ve also had live logging up during testing to see if that would provide a clue but no.
You should set up a complete piston…Include the 'if" and the “then” parts…then, click the test button…it will run the piston. You can turn on logging, full, prior, and then hit test, that way you can see what happens. After that, you should be able to click trace and then it will break down the statements for you, which you need to know if you are looking for certain things within the logging.
Thank you for assisting. I don’t know what you mean by complete piston, this piston is designed to be called external, it has no triggers, nothing is subscribed. I have 29 other pistons and 5 of those have no triggers but are called, they all have the Trace Toggle. In any case I added an if device is on then… with subscribed device, tested it, edited it, closed it, still no Trace Toggle. Note Full tracing has always been on. I performed the above several times. Are there conditions where you would not expect a Trace Toggle?
Update: I cloned the piston and did the same testing, no Trace Toggle. Just making sure something wasn’t corrupted. Something I’m doing in this piston must be wrong, next test will be start taking pieces out one at a time to see what happens.
I would take a green snapshot of it and post it on here. The minions will be happy to help 
Well I identified a segment of code that when disabled the Toggle returns. This segment of code is what I need to trace of course 
So before I ask for code help, are there processing limits in webcore that would interrupt a piston? The segment does a sort on 2 small (<30 elements) lists.
I think this was resolved in another thread: my code was definitely timing out, using more than 20 seconds of processing which is an ST limit. Because it was timing out less than half way through processing, its very possible the logs and Toggle were interrupted. I was able to somewhat prove this by testing with a smaller data set, and with the exact same code the piston did what it was supposed to, logs worked, and Toggle appeared.
Bottom Line: If your Trace Toggle doesn’t work, you may be timing out.
