1) Give a description of the problem
Piston works within 1-2 seconds sometimes - other times could be 5 minutes
2) What is the expected behavior?
If any of the listed switches turns on and a specific switch is off, then turn on a switch for 90 seconds then turn it back off.
3) What is happening/not happening?
Sometimes it works as expected. Other times the trigger is hit but the action does not execute for up to several minutes.
**4) Post a Green Snapshot of the piston![image|45x37]
My guess would be multiple triggers backing up full execution of your piston… but without a log, that’s all anybody can do is guess.
Can you turn on full logging and post a sample from delayed execution?
Are all of your switches Zwave/Zigbee, or do you have any WiFi devices (TP-Link, Wemo, iHome) that depend on having the command sent to a cloud server before coming back to the device/hub? If both the any of device triggering the piston and switch 69 are dependent on a cloud service, then I could definitely see several seconds of latency being “normal” (although obviously undesirable).
I turned on logging, waiting for the problem to happen before I post the logs. Since yesterday I have not observed the misbehavior.
LOL, the good ol’ Hawthorne effect! Gets me every time. 
Just a thought while we wait for it to tell us something in the logs… do you by chance have a piston that turns on a bunch of those lights at the same time? I wonder if the piston is being swamped by switch updates and falling on its face temporarily.
All switches in this piston are Zwave. I was under the belief that all webCoRE functions happen in the cloud - are any processed locally?
I’m not the expert by any stretch, but I gather that there are 2 clouds: Webcore and SmartThings. You write a piston in the Webcore cloud and, when it gets activated, it gets put in the ST cloud. So in that respect, yes, all functions communicate with the ST cloud, whether they originate from a physical device or are responding to programmed triggers/conditions.
I was speaking more about devices and how they’re connected. Zwave & Zigbee devices only have to communicate with the ST cloud once because they talk directly to the hub. If you have a WiFi device, it has to communicate with it’s own cloud first, then the ST cloud (if the end-device is connected via your hub). Compound latency.
Ah, gotcha. Was thinking ST cloud as “some” ST apps run “locally” on the hub and do not have to actually communicate with ST cloud.
