Webcore, force every block to execute

[nh.schottfam]

You can at the top of the piston set variables for what you want to happen based on triggers, then below that just evaluate your variables for what to run.

You likely won't use 'every' (as it is its own block that exits), but you could have a variable for when next to run.

You can put into the end of the piston the triggers

ie

Time happens daily at a time,

or Date & Time happens daily at variable

See:

Some webCoRE Basics for writing pistons - Trigger aggregation

This is another example of using triggers in a webCoRE piston As many of you may know, if a piston does not use any trigger comparisons, webCoRE will attempt to upgrade condition comparisons to a trigger (subscription). If your piston only uses condition comparisons, many times this is an easy way to code (ie only use condition comparisons). The challenge sometimes, is you need/want a trigger comparison, and now all your condition comparisons are no longer subscribed to (automatically as …