Piston Aborts Sequence Randomly

[automatican]

I have a piston that triggers at a specific time then runs a host of sequential commands for a hue light. This sequence happens over ~60 minutes. However, this piston often randomly halts and proceeds to schedule the event for the next day without completing all the steps in the sequence. Can anyone assist in determining if this is a bug in webcore, or is come type of system limitation on the time required to complete a triggered piston.

Here is the piston:

Here are the last part of the logs showing it schedule the task agains for the next day before completing:

11/2/2017, 6:50:52 AM +344ms
+1ms ╔Received event [Home].time = 1509619853808 with a delay of -1464ms
+450ms ║RunTime Analysis CS > 33ms > PS > 292ms > PE > 125ms > CE
+465ms ║Piston waited at a semaphore for 259ms
+468ms ║Runtime (40236 bytes) successfully initialized in 292ms (v0.2.0fb.20171026) (466ms)
+469ms ║╔Execution stage started
+470ms ║╚Execution stage complete. (2ms)
+472ms ║Setting up scheduled job for Fri, Nov 3 2017 @ 6:30:00 AM EDT (in 85147.185s)
+501ms ╚Event processed successfully (501ms)
11/2/2017, 6:50:52 AM +149ms
+0ms ╔Received event [Home].execute = recovery with a delay of 106ms
+153ms ║RunTime Analysis CS > 16ms > PS > 38ms > PE > 100ms > CE
+172ms ║Runtime (40159 bytes) successfully initialized in 38ms (v0.2.0fb.20171026) (171ms)
+173ms ║╔Execution stage started
+182ms ║║Comparison (time) 24652329 happens_daily_at (time) 23400000 = false (1ms)
+184ms ║║Cancelling condition #17’s schedules…
+184ms ║║Condition #17 evaluated false (5ms)
+186ms ║║Cancelling statement #17’s schedules…
+188ms ║║Requesting time schedule wake up at Fri, Nov 3 2017 @ 6:30:00 AM EDT
+191ms ║║Cancelling condition #1’s schedules…
+192ms ║║Condition group #1 evaluated false (state changed) (12ms)
+203ms ║╚Execution stage complete. (30ms)
+205ms ║Setting up scheduled job for Fri, Nov 3 2017 @ 6:30:00 AM EDT (in 85147.647s)
+246ms ╚Event processed successfully (246ms)
11/2/2017, 6:50:45 AM +355ms
+0ms ╔Received event [Home].time/recovery = 1509619815801 with a delay of 29553ms
+172ms ║RunTime Analysis CS > 27ms > PS > 36ms > PE > 110ms > CE
+185ms ║Runtime (40172 bytes) successfully initialized in 36ms (v0.2.0fb.20171026) (184ms)
+186ms ║╔Execution stage started
+333ms ║║Executed physical command [Hue color lamp 201].off() (137ms)
+395ms ║║Executed physical command [Hue color lamp 201].on() (50ms)
+463ms ║║Executed physical command [Hue color lamp 201].off() (57ms)
+497ms ║║Executed physical command [Hue color lamp 201].on() (25ms)
+530ms ║║Executed physical command [Hue color lamp 201].off() (24ms)
+562ms ║║Executed physical command [Hue color lamp 201].on() (25ms)
+592ms ║║Executed physical command [Hue color lamp 201].off() (22ms)
+627ms ║║Executed physical command [Hue color lamp 201].on() (26ms)
+657ms ║║Executed physical command [Hue color lamp 201].off() (22ms)
+688ms ║║Executed physical command [Hue color lamp 201].on() (23ms)
+727ms ║║Executed physical command [Hue color lamp 201].off() (33ms)
+768ms ║║Executed physical command [Hue color lamp 201].on() (33ms)
+806ms ║║Executed physical command [Hue color lamp 201].off() (30ms)
+1009ms ║║Executed physical command [Hue color lamp 201].on() (195ms)
+1051ms ║║Executed physical command [Hue color lamp 201].off() (34ms)
+1093ms ║║Executed physical command [Hue color lamp 201].on() (32ms)
+1098ms ║║Fast executing schedules, waiting for 1355ms to sync up
+2488ms ║║Executed physical command [Hue color lamp 201].off() (29ms)
+2492ms ║║Fast executing schedules, waiting for 1960ms to sync up
+4485ms ║║Executed physical command [Hue color lamp 201].on() (27ms)
+4487ms ║║Fast executing schedules, waiting for 1966ms to sync up
+6504ms ║║Executed physical command [Hue color lamp 201].off() (44ms)
+6505ms ║╚Execution stage complete. (6319ms)
+6509ms ║Setting up scheduled job for Thu, Nov 2 2017 @ 6:50:53 AM EDT (in 1.945s), with 5 more jobs pending
+6537ms ╚Event processed successfully (6537ms)

[bobbles]

The tasks may be cancelling because when you get deep into the actions, the time is no longer true so the tasks will cancel.
Click on the WITH and go into the settings cog.
Change Task Cancellation Policy (TCP) to never.
This way all the tasks will run.

[automatican]

Thanks for the advice. I will try that and report back (after a few successful days) if it works, or right away tomorrow if it doesn’t.

I know I could also create numerous pistons to start at the various times, but it is much less simple to manage.

[bobbles]

When the piston is running you can click on the trace button and see the timers counting down.

[automatican]

This piston has now run as expected 4 days in a row after the change. So this appears to have done the trick. Thanks!